Omphile Matheolane at DDD Europe 2025
summary
Uses a bank example to show bounded contexts as separate modules — accounts, payments, loans, CRM — each with its own domain model and rules and deployed independently. Asserts boundaries prevent logic leakage and require no shared mutable state, forbids direct cross-context updates, and recommends explicit contracts: public interfaces or domain events for communication. Emphasizes modeling decisions that enforce these constraints rather than vague modularity goals, and treats interfaces/events as the default integration mechanism.
AI-written summary · about
related talks
42mBounded Context — How to Modularize a System in a Few Steps
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
42mBounded Context: Keep It Simple!
47mThe Joy of Multiple Models
49mDDD & Microservices: At Last, Some Boundaries!
01h 00mFrom Domain Driven Design DDD to Delivery
39mFrom Domain Boundaries to Software Architecture
56mDDD in Microservices: Complexity versus Complexity