{"product_id":"event-driven-architecture-pocket-guide-saga-cqrs-outbox-and-the-traps-nobody-warns-you-about-9798258870285","title":"Event-Driven Architecture Pocket Guide: Saga, CQRS, Outbox, and the Traps Nobody Warns You About","description":"\u003cp\u003e • Author(s): Gabriel Anhaia\u003cbr\u003e • Publisher: Independently Published\u003cbr\u003e • Publisher Imprint: Independently Published\u003cbr\u003e • BISAC: Software Development \u0026amp; Engineering - General\u003c\/p\u003e\u003cp\u003e\u003cb\u003eLook at any business workflow and decide - on purpose - whether to model it request-response or event-driven, then pick the right patterns (outbox, saga, CQRS, event sourcing) without over-engineering or under-engineering.\u003c\/b\u003e \u003c\/p\u003e\u003cp\u003e\u003c\/p\u003eYou shipped request-response services for years. Now a product manager wants an event-driven one - or you inherited one already in production and it is groaning under its own complexity. Dual writes are losing messages. A saga compensates halfway and leaves orphaned state. Consumers break every time the event schema changes. Somebody added Kafka because \"it scales,\" and now nobody can trace a request end to end. You need the patterns, the trade-offs, and the anti-patterns spelled out - fast, without wading through 600 pages of abstract theory. \u003cp\u003e\u003c\/p\u003e\u003cb\u003eEvent-Driven Architecture Pocket Guide\u003c\/b\u003e is the working engineer's reference for building event-driven systems that do not collapse under their own weight. Across \u003cb\u003e15 chapters and five parts\u003c\/b\u003e, it covers the whole landscape as of 2026 - Kafka 4.0, Redpanda, Pulsar 4.1, NATS JetStream, RabbitMQ quorum queues, Debezium 3.x, Confluent and Buf schema registries, Temporal, AWS Step Functions - and shows exactly when each pattern earns its complexity budget and when it becomes the wrong tool. \u003cp\u003e\u003c\/p\u003eWhat you will take away: \u003cbr\u003e- \u003cb\u003eCommands vs events\u003c\/b\u003e - the subtle tense difference that determines whether your system scales or calcifies, and where architectural drift in event-driven systems actually starts.\u003cbr\u003e- \u003cb\u003eThe outbox pattern done right\u003c\/b\u003e - why dual writes lose data, how to implement the production-proven fix on Postgres \/ MySQL, and the \"we tried two-phase commit\" cautionary tale.\u003cbr\u003e- \u003cb\u003eSaga, CQRS, event sourcing\u003c\/b\u003e - orchestration vs choreography, when to split reads from writes, when the log IS the database, and the three common traps for each.\u003cbr\u003e- \u003cb\u003eBroker trade-offs on six axes\u003c\/b\u003e - throughput, latency, ordering, retention, cost, and operational burden - for Kafka, Pulsar, NATS, RabbitMQ, and Redpanda.\u003cbr\u003e- \u003cb\u003eTwelve real system designs\u003c\/b\u003e - e-commerce orders, Stripe-style payments, IoT telemetry, ride-share dispatch, video encoding, fraud detection, inventory, notifications, and more - each walked from requirements to chosen stack to exit criteria.\u003cbr\u003e- \u003cb\u003eAnti-patterns that wreck production\u003c\/b\u003e - events used as commands, the event-driven monolith, missing contract tests, no backpressure strategy, message-bus-as-database - with the recovery paths that actually work. \u003cp\u003e\u003c\/p\u003ePrimary code examples are in Java 21 (Spring Boot \/ Micronaut) because Kafka + Spring is the dominant production stack. Python 3.13 and Go 1.24 snippets carry the lighter examples. Schema samples cover Avro, JSON Schema, and Protobuf. Every version is locked to April 2026 and web-verified in the fact-check pass. \u003cp\u003e\u003c\/p\u003e\u003cb\u003eWho this book is for: \u003c\/b\u003e backend and platform engineers being asked to build event-driven systems, tech leads choosing between EDA and request-response for a new system, and anyone who inherited an event-driven system and needs to keep it running without rewriting it. Baseline assumed: you have shipped at least one production service; you know SQL, HTTP, and what a queue is. \u003cp\u003e\u003c\/p\u003e\u003cb\u003eOther books in Pocket Guides for Developers\u003c\/b\u003e (standalone, no reading order): \u003cbr\u003e- \u003ci\u003eSystem Design Fundamentals\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003eSystem Design Interviews\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003eAI Agents Pocket Guide\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003ePrompt Engineering Pocket Guide\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003eDatabase Playbook\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003eLLM Observability Pocket Guide\u003c\/i\u003e\u003cbr\u003e- \u003cb\u003eThis book\u003c\/b\u003e - \u003ci\u003eEvent-Driven Architecture Pocket Guide\u003c\/i\u003e\u003cbr\u003e- \u003ci\u003eRAG Pocket Guide\u003c\/i\u003e \u003cp\u003e\u003c\/p\u003eCompanion handbook: \u003ci\u003eObservability for LLM Applications\u003c\/i\u003e (The AI Engineer's Library, Book 1).","brand":"Independently Published","offers":[{"title":"Paperback","offer_id":47883408244887,"sku":"9798258870285","price":1719.0,"currency_code":"INR","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0666\/3471\/1191\/files\/9798258870285.webp?v=1781101684","url":"https:\/\/atlanticbooks.com\/products\/event-driven-architecture-pocket-guide-saga-cqrs-outbox-and-the-traps-nobody-warns-you-about-9798258870285","provider":"Atlantic Books","version":"1.0","type":"link"}