Data management track

What it covers

• Database per Service Each service owns its data. Everyone else reaches it through the service's API or events.
• Shared Database Several services read and write the same database. Simple at first, and the main thing that stops services being independent.
• Saga Run a multi-service business transaction as local transactions plus compensating actions.
• Transactional Outbox Save the data change and the event it must produce in one local transaction, then publish from that table.
• API Composition Answer a query that spans services by calling each one and combining the results.
• CQRS Use one model to handle commands that change state and separate read models built for the queries you need.
• Event Sourcing Store every state change as an immutable event and derive the current state by replaying them.
• Change Data Capture Turn every committed database change into an event by reading the database's own transaction log.
• Saga lab Run an order across inventory, payment and shipping. Fail a step and watch the compensations run, then add missing refunds, duplicate messages and failed compensations. Switch between orchestration and choreography.
• Transactional Outbox lab Crash a service between its database write and its event publish, and count lost events, ghost shipments and duplicates. Then switch on the outbox and an idempotent consumer and compare.