Dynamic Consistency Boundaries
Consistency boundaries form per-operation, not per-schema
HandlePlaceOrderCommand
OnPaymentReceivedEvent
ConfirmShipmentCommand
Shipping
Order
Discount
Pricing
Customer
Ledger
Fulfillment
Cart
Tax
Product
Address
Invoice
Warehouse
Inventory
Payment
Return
Refund
Subscription
Coupon
Notification
HandlePlaceOrderCommand
OnPaymentReceivedEvent
ConfirmShipmentCommand

Dynamic Consistency Boundaries

DCB lets you define consistency scopes per operation: a temporary bubble that holds only the data the transaction actually needs. so your architecture can evolve with the business instead of resisting it.

Move past the aggregate as the organizing unit of your event store

Retire snapshots: A workaround finally made unnecessary with DCB

Start with good-enough boundaries and refine them as the domain reveals itself

Tag events with multiple semantic labels instead of pinning them to a single aggregate ID

Pivot from customer-centric to account-centric (or anything else) without migrations or lost history