A monolith runs interface, business rules, and data access in one application. In-process calls make deployment and tracing straightforward.
The demo shows one module change moving through a shared build and release. As the codebase grows, clear module boundaries help prevent unrelated changes from affecting each other.
When to use
Consider it when starting a product with low operational overhead or when one strong transaction boundary helps.