My uni course on optimization was so much fun but I forgot all of it. This was a nice reminder that I should probably revisit the basics :)

Vancouver Public Library as well :) https://www.vpl.ca/digital-library/oreilly-technology-and-bu...

Though I wish I could check them out on my Kobo...

I love this website. I wish I could search it in Spanish. I grew up watching the Simpsons in Spanish and I sometimes struggle to find the right clip because I don't know the exact translation

I hang up a flag on my balcony and it has worked for me.

I worked for AWS for two years and if I recall correctly, one of the issues was circular dependencies.

I experienced that too! In Canada. It was a head-scratcher, none of my teammates had issues, and i could access just fine on my phone but i couldn't on my home's wifi.

Same. Fraser Valley?

I love this. Well, in general, I love illustrated explanations :)

"Synchronized demand is the moment a large cohort of clients acts almost together. In a service with capacity ... requests per second and background load ..., the usable headroom is ..."

To the author of the article: I stopped reading after the first two sentences. I have no idea what you are talking about.

"Synchronized demand is the moment a large cohort of clients acts almost together."

Imagine everyone in a particular timezone browsing Amazon as they sit down for their 9 to 5; or an outage occurring, and a number of automated systems (re)trying requests just as the service comes back up. These clients are all "acting almost together".

"In a service with capacity mu requests per second and background load lambda_0, the usable headroom is H = mu - lambda_0 > 0"

Subtract the typical, baseline load (lambda_0) from the max capacity (mu), and that gives you how much headroom (H) you have.

The signal processing definition of headroom: the "space" between the normal operating level of a signal and the point at which the system can no longer handle it without distortion or clipping.

So headroom here can be thought of "wiggle room", if that is a more intuitive term to you.

Is the pragmatic solution to return 503 and have clients back off.

Or, if possible make latency a feature (embrace the queue!). For service to service internal stuff e.g. something like a request to hard delete something, this can always be a queue.

And obviously you can scale up as the queue backs up.

I do love the maths tho!

"Developers still use Stack Overflow and other human sources of expertise"

press X to doubt

"So you write the answers yourself?"

"No, the developers do that."

"So you must take the answers to the person with the question?"

"Well, no... my LLM does that!"

"...what would you say you DO here?"

"I'm an answer website! What don't you people understand?!"