Omphile Matheolane speaking at DDD Europe
summary
Argues that a monolithic bank codebase becomes manageable by carving out accounts as its own bounded context and loans as its own bounded context, wiring them through domain events or public APIs so they evolve independently. Recommends extracting shared logic into utilities to avoid duplication, claims this structure enables independent deploys and reduces coupling, and shows how clear boundaries plus event-driven communication keep modules consistent without a central orchestrator.
AI-written summary · about
related talks
02h 29mPractical advice for building glorious monoliths
45mUsing DDD To Decompose Your Monolith
01h 00mDomain-Driven Architecture at Scale
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
23mData Mesh Architecture in Banking
52mBuilding monolith applications that could scale to microservices..
01h 29mMonolithic Delivery
01mJohannes Rost