Posts Tagged "Architecture"
There's More Than One Way to Get Observability Right
The specialize-versus-unify argument feels like a religious war. It isn't. Both sides are right — they're answering different questions. There are several ways to get observability right. The way to get it wrong is to never ask which one you're building for.
Read Post
Continuous Acceptance Tests
An acceptance test run once before deploy proves the data was correct for one instant. The data does not stay correct because the deploy was green. Stop retiring your best test the moment it passes. Run it forever.
Read Post
'Can' vs 'Does'
The difference between a system that can fail and a system that does fail is time. Murphy's Law is not a joke. It is a design constraint. Every moving part you add is another bet against the house, and the house always wins.
Read Post
"Design Me a Highly Resilient Database"
There is no such thing as a "highly resilient database" in the abstract. The right answer starts with understanding the problem — the data, the product, the failure modes, the regulatory environment — not a product name.
Read Post
Puppets and Octopi: Why Top-Down Orchestration Hits a Wall
Centralized, imperative orchestration requires centralized coordination, and centralized coordination is a bottleneck that doesn't scale. Distributed, declarative convergence pushes intelligence to the edges.
Read Post