modular-monolith-3-process-correct-for-3eng-1000user

For a 3-engineer team building to 1000 internal users on a 6-month deadline, a modular monolith with 3 deployable processes (api, worker, web) and 1 codebase is the right topology. Module boundaries are enforced via Python package structure with service interfaces — not microservice networking — preserving the extraction path for year-2 without today’s distributed complexity.

Related

• r-dash-modular-monolith-3-process-topology
• modular-monolith-correct-for-small-team-single-tenant-intern
• r-same-local-repo-and-monorepo-topology
• docker
• r-dash-architecture-freeze-checkpoint-2