Insights
Engineering notes, infrastructure deep dives and practical guides from the Exotecho team.
The claim When something in your application behaves unexpectedly — a customer was charged the wrong amount, an order was routed to the wrong warehouse, a discount was or was not a...
Read article
The claim Every queue in your system — the job queue, the message buffer, the retry backlog, the in-memory list of pending work — has a maximum size, and if you did not choose that...
Read article
The claim Deciding what your web application does based on which browser it thinks the visitor is using — reading the user-agent string and branching on it — is a technique that ha...
Read article
The claim When an application is slow, the instinct is to make the slow work faster — optimise the query, add the cache, upgrade the hardware. The larger and cheaper win is usually...
Read article
The claim The hardest part of caching is not storing a value; it is knowing when the stored value has become wrong. Teams reach for elaborate invalidation schemes — tracking every...
Read article
The claim A single slow database query, left to run without a time limit, can bring down an entire application — not because the query itself is important, but because while it hol...
Read article
The claim The software your business runs is only as reliable as your ability to rebuild it from source, and most teams discover far too late that they cannot. The application depl...
Read article
The claim Any operation that changes something and can be retried — a payment, an order, a message send — will eventually be retried after it already succeeded, because the network...
Read article
The claim Most application bugs and a large share of security holes come from the same root cause: data that entered the system in a shape the code did not expect, and was trusted...
Read article
