Sagas + Distributed Transactions - A Practitioner's Handbook: Payment, Entitlement, Library Sync, and Email Receipt Across Services — Without Two-Phase Commit #1007371

A practitioner's handbook on building sagas for distributed transactions, told through one running example: a digital reading platform's purchase flow — charge the card, grant access, sync the library, send the receipt — spanning four services with no shared database and no distributed lock. Starting from why cross-service transactions don't compose and why two-phase commit isn't the answer here, the book builds the same purchase saga three times: as an orchestrated state machine, as a choreographed event chain, and as a hybrid of both — then hardens it with durable crash recovery, idempotent retries, timeout and dead-letter handling, safe versioning for saga definitions already in flight, and distributed tracing. It closes with a full case study assembling every mechanism into one system and tracing a real purchase through its success path, its failure path, and a mid-flight crash. Code samples are TypeScript; the patterns transfer directly to any stack.