Book: Event-Driven Architecture Pocket Guide My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me: xgabriel.com | GitHub Picture the team that spends four months migrating an order-processing service to full event sourcing because checkout keeps losing partial-failure state. They build an event store, projections, snapshots. Six months later, the same partial-failure bug shows up in a different shape: payment captured, inventory reserved, shipping never booked, no compensating action ever ran. They built the wrong pattern. They needed a saga. The event store was useful, but it solved a problem they did not have yet, and the problem they did have was still in production. The reverse mistake is just as common. Teams reach for sagas when their actual pain is "we cannot reconstruct what happened during yesterday's incident because we only store the current state." Compensations do not give you history. An event store does.…