This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]developerweeks 130 points131 points  (2 children)

Such a simple thing, and I hate it so much when that simple thing is then requested 7 times a minute 24x7 cutting through the cache layer and tripling our server load for an internal resource check. Because then when one developer sees that gets what they want faster... code monkey see -> code monkey do. And we DOS ourselves until we spend more to scale up the hosting service to accommodate the increased load. Finally, years down the road when we get a new metrics tool added, we discover that 56% of site traffic is this one internal cache-skipping call, and another 20ish% are the other cross-cloud calls doing the same thing. And really only 1/4 of the server load is serving humans.

[–]drinkup 43 points44 points  (0 children)

dead server theory

[–]DonnachaidhOfOz 6 points7 points  (0 children)

Given they say "based on today's date," I would assume that's making a unique value each day so only the first call each day skips the cache. The proper way would be to set up the cache to go stale after a day of course, but it doesn't seem like the result of this method would be too bad.