sapkalsachin2011/sagapattern

This is an orchestrated order-processing Saga: a client submits and polls an order; the API persists it and publishes an event; the Saga coordinates inventory reservation and payment, then confirms the order or compensates by releasing inventory. Workers keep service-owned state, while the API and notification worker consume status changes. The README documents the principal message flow and scenarios; sampled source confirms API submission, inventory reservation, and service persistence setup, but not every consumer or the state machine implementation.