Starting a new project with a monolith might sound old-fashioned, but it’s often the smartest path toward a scalable microservice architecture. When service boundaries are unclear, jumping directly into microservices can create unnecessary complexity, duplicated effort, and painful rework. A modular monolith, on the other hand, gives you the flexibility to refine domain boundaries while keeping development simple and cost-effective.

In this talk, I will share a practical approach to designing and implementing a monolith that is intentionally structured for future transformation into microservices. You’ll learn how to define clean module boundaries, how to keep coupling under control, and which design decisions today will save you major effort tomorrow. Attendees will walk away with a clear mental model and concrete patterns for building modular applications that start small but are prepared to scale into distributed systems when the time is right.