Modular Monolith (TypeScript, NestJS, Prisma, PostgreSQL, BullMQ, Docker) overview

A TypeScript monolith deliberately structured into independent modules with explicit boundaries, combining the deployment simplicity of a monolith with the organizational clarity of microservices. Each NestJS module owns its Prisma schema slice and communicates with others only through published events or well-defined service interfaces. BullMQ handles async work within module boundaries, and Redis backs both the job queue and cross-module event bus. PostgreSQL schemas enforce data ownership per module. Docker Compose runs the complete system locally. The tradeoff is the constant vigilance needed to prevent module boundaries from eroding, but when maintained, this pattern avoids distributed-system complexity while preserving the option to extract modules later.