After three years of scaling a Django monolith, our deploy times stretched past 45 minutes and a single failing test could block the entire team. We did not jump straight to microservices. Instead, we drew service boundaries inside the monolith first, enforcing them with module-level import rules and shared nothing between domains.

The first boundary we extracted was the billing domain. It had the clearest API surface: create invoice, process payment, issue refund. We moved it behind an internal HTTP interface, kept the same database for six months, then migrated to its own PostgreSQL instance once we trusted the boundary. Deploys for billing went from 45 minutes to under 3.

The lesson was not that monoliths are bad. The lesson was that boundaries matter more than infrastructure. A well-structured monolith with clean domain separation will outperform a distributed system with tangled dependencies every time. Start with boundaries, extract services only when you have a concrete operational reason.