I like solving problems. My dream job is to get paid to learn (and do cool stuff with that knowledge). When I'm not writing software, I'm making things out of wood, or baking something in the kitchen.
That was a really interesting read. I found myself on a project a little while ago that would have really benefited from knowing about that nginx setting. Long story short, there was a web service (we'll call it A) that made a call to another web service (we'll call it B). A would need to calculate something, so it would make a call to B to fetch and cache some data. Often, when the user made a request to A, A would end up making several calls to B for the exact same data. If we hit B with several simultaneous calls, the first call to it would succeed while the rest would fail (for a reason... it's complicated). Since all the calls in that set of calls from A to B were the same, we totally could have reduced it to just a single call to B.
Senior Engineering Manager at GitHub, building APIs.
Passionate about fostering strong engineering cultures in distributed organizations.
Husband and dad of 4.
Thanks Joel, appreciate that! I agree with you - that nginx config would have saved you a lot of pain and debugging for this use case. I find that it's not a well-known config.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That was a really interesting read. I found myself on a project a little while ago that would have really benefited from knowing about that nginx setting. Long story short, there was a web service (we'll call it A) that made a call to another web service (we'll call it B). A would need to calculate something, so it would make a call to B to fetch and cache some data. Often, when the user made a request to A, A would end up making several calls to B for the exact same data. If we hit B with several simultaneous calls, the first call to it would succeed while the rest would fail (for a reason... it's complicated). Since all the calls in that set of calls from A to B were the same, we totally could have reduced it to just a single call to B.
Thanks Joel, appreciate that! I agree with you - that nginx config would have saved you a lot of pain and debugging for this use case. I find that it's not a well-known config.