Why CRDTs can't handle financial ledgers, how Event Sourcing made auditors thank us for the first time in 10 years, and a Distributed Saga that survived a transatlantic cable cut.
This is Part 3 of the Architecture of Chaos series. Start from Part 1 | Part 2
Chapter 5: Why CRDTs Fail for Financial Ledgers (Event Sourcing)
The Critical Meeting
Fifth month. CFO Masato called me in. Compliance team plus two external auditors present. The question was simple:
"Selim, how do we guarantee balances are correct in the new architecture? Auditors need to trace every transaction. They need to see where every cent came from and where it went. Can this 'CRDT' thing provide that?"
In standard CRUD apps, if a user updates their profile name, you overwrite the database row. No big...
Cell-Based Architecture for GDPR, Hybrid Logical Clocks (the poor man's TrueTime), fencing zombie leaders during split-brain,…
The Problem We Were Actually Solving Our CQRS model kept Events in a separate Kafka...
You build the feature. You test it. It works. Three months later: data is missing, a transaction...
Expense tracking usually fails not because of the interface, but because of the hidden friction in reconciliation and audit…
Decisions are already distributed. Accountability isn't. That's the gap to close.
