Even the fastest web servers become bottlenecks when handling CPU-intensive API work. Slow response times can cripple your service, especially when paired with an API gateway that times out after 29 seconds.
I solved this using a simple middleware that eliminated 504 - Gateway Timeout responses and significantly reduced unnecessary load on my service API.
AI tries to make everything easy… convenient, but life without discomfort is not something to desire. The label ‘PC compatible’ is a reminder of how complex (inconvenient) things can be.
Read more...
… did quite a lot, actually. Apparently, when you sit down and think about it, happenings start to surface.
Read more...
The other day, I was taken back to the “good old days”, and not in a good way. I had assumed that a major hardware provider like Samsung nowadays would ensure a decent user experience during firmware updates, regardless of the operating system. But I was in for a disappointment.
My home server running Linux has been crashing occasionally for a while. But since a reboot would temporarily “fix” it, sometimes for weeks, I never prioritized finding the underlying problem… until now. It feels like a recent kernel update now triggers the crash more often, but I have no data to back this statement up.
Read more...
Applying retry strategies on API calls to make them more robust often brings its own set of problems. Occasionally, rather than losing an entity-creating call, you end up with multiple, and trust me — duplicates are a pain to clean up.
However, idempotency can neutralise the inconveniences from retries, making the pair a powerful combo. 💪
Read more...The posts touch a lot of different topics in no particular order. It might be more convenient to browse by tags if you have a topic of specific interest.