Monolithic Architecture

A monolith packages the entire application into one deployable unit. It is straightforward to build, test and deploy, which makes it a strong default for small teams or early stage products.

When it fits

• Simple product scope: one team, a clear domain, modest scale
• Rapid iteration: single repository, single pipeline, easy refactors
• Tight consistency: one database, transactional guarantees

Risks

• Slower builds as code grows
• Scaling requires scaling everything together

Real‑world examples

• Basecamp runs a well‑known Rails monolith to this day
• GitLab began and still operates primarily as a large Ruby on Rails monolith with modular boundaries

Practical tips

• Keep clear module boundaries inside the monolith to avoid a big ball of mud
• Extract shared libraries and domain modules early to prepare for future growth