🚀 Launching today: 28 Days of #DistributedDilemmas
Follow me on Twitter/X this February for one battle-tested insight a day on the hidden complexities behind outages, tech debt and architectural nightmares.

Follow me on Twitter/X for one battle-tested insight daily in your feed this February to dive into the hidden complexities behind outages, tech debt, and architectural nightmares!
Catch up #DistributedDilemmas on Twitter/X! 👈
No hype. No fluff.
Just hard-earned engineering wisdom.
Update, end of February 2025: I made it to day 24. All 24, with the diagrams, are collected in #DistributedDilemmas: all 24 days in one place.
Keep reading
Day 3 of #DistributedDilemmas: Caching accelerates inconsistency
Caching accelerates inconsistency. Cache invalidation storms often outweigh hit rates. The fastest cache is sometimes no cache at all. Exhibit A: DoorDash…
Day 4 of #DistributedDilemmas: Idempotency is a lie we tell ourselves
Idempotency is a lie we tell ourselves. Nested partial failures expose retry logic flaws. True exactly-once delivery remains elusive in distributed…
Day 2 of #DistributedDilemmas: Microservices don't eliminate complexity, they redistribute it
Microservices don't eliminate complexity, they redistribute it. Your monolith's function calls become network calls. Pick which failures you want to debug…
Leave a comment