An autonomous bubble is a bounded context that owns its persistence and can evolve without breaking other contexts or a legacy model. It reduces coupling between both models and teams, making independent change possible. section 12.5
Adopt autonomy progressively:
- Refactor code into a bounded context while temporarily retaining a shared database schema. section 12.5
- Move the context to its own persistence schema when database coupling becomes the remaining migration risk. section 12.5
- Publish domain events and use an anticorruption layer to translate changes for the legacy model. section 12.5
Gigs-platform modernization
A gigs platform separated job drafting and job fulfillment into new bounded contexts. A Job Published event was translated by an anticorruption layer into the legacy model, enabling A/B testing and gradual migration while existing functionality remained operational. section 12.5
Figure 12.29 Moving to an autonomous bubble to decouple from the legacy model using an event handler to update the legacy model with changes from the bounded context
Shows the transition from a shared or legacy model to an autonomous bubble, including event-driven updates. section 12.5
