// Insights
Management content for technical leaders — infrastructure warning signs, key decisions, and the real cost of unstable systems.
7 articles
Conversations about fault tolerance usually dive into technical details within the first two minutes: replication, failover, timeouts, quorum. The executive is left to assess the proposal based on the speaker’s …
Read morePeople rarely talk about excessive reliability: insufficient reliability announces itself with outages, while excess looks like a virtue. A company pays for complexity it doesn’t use, and calls it prudence. …
Read moreTo the question “Do we have backups?” a technical specialist almost always answers affirmatively, and answers honestly: there’s a job in the scheduler, files are being created, space is being used. The manager mentally …
Read moreIn most companies the infrastructure diagram exists in two forms. The first is a pretty presentation: clusters, replicas, load balancers, arrows between them. The second is the real one — in a single engineer’s head — …
Read moreWhile infrastructure is working, it looks like an item in the expense report that you want to cut. Once it fails — the tone flips: engineers ask for a budget for “proper reliability”, the CFO looks at the estimate, and …
Read moreFault tolerance is not a binary state. It’s a ladder of four levels, and each solves its own problem at its stage of the product’s life. Trying to skip a rung and build a complex system too early is classic …
Read moreInfrastructure rarely breaks in a single day. Usually it degrades unnoticed — month by month, bit by bit. The team gets used to inconveniences, calls them quirks, and things go on — until they don’t. People usually …
Read more