Monolithic architecture
An architecture in which all parts of an application are developed together in a single codebase and released as one unit.
- 01
Why it matters
A monolith is the simplest path for development, testing and release, especially at the start and in small teams. Problems begin when the code becomes disorganised and boundaries between parts blur. A well-modularised monolith is also ready to be split up when needed.
- 02
Example
A start-up builds its product as a single application but separates ordering, invoicing and notifications into clear modules. Years later, the notification module is easily moved to a separate service because of load.
- 03
Common mistake
Dismissing the monolith as “old-fashioned” and splitting it too early, or letting it turn into code with blurred boundaries where everything depends on everything.
- 04
Related terms
Related services and guides
Let's talk about your project.
Tell us what you need; we will define the scope together.