This reads like LLM noise, with headings missing articles.

It also doesn't mentionn the most obvious solution to this problem: adding a random factor to retry timing during backoff, since a major cause of it is everyone coming back at the precise instant a service becomes available again, only to knock it offline.

▲

glhaynes 3 days ago | parent | next [-]

I don't associate missing articles with LLMs and I've known people, always for whom English was a second language, who dropped them often.

	▲	raffraffraff 3 days ago \| parent [-]
		If anything I'd say that "excellent formatting" with fancy headings and formatting is the hallmark of llm

▲

vlovich123 2 days ago | parent | prev [-]

That works when you control the client but not when you have a case like this fetching state from a DB. For that you do in fact need some kind of locking mechanism, although it’s better if it’s implemented within the cache as a pass through cache that parks the concurrent requests except one if an outbound is needed rather than hitting the database directly. That’s how Cloudflare’s CDN works to minimize requests into the origin.