Monolith
ExplainedConcept
Also known as: Monolithische architectuur
Architectural style where the whole application is built and deployed as one cohesive unit.
Monolith, explained
Written by EduVerseWhat it is
A monolith is an application built and deployed as one unit: one codebase, one build, usually one database. All features, from login to invoicing, live in the same program and call each other as ordinary function calls rather than over the network.
Why teams use it
A monolith is simple to develop, test and deploy: one repository to clone, one app to run locally, one place to debug. That’s why many new products start this way. The pain comes later, when the codebase grows, builds slow down and many teams have to coordinate every release. Splitting into microservices is one answer, but not the only one.
An example from work
On your first day you clone one repository, run ./mvnw spring-boot:run, and the whole system starts on localhost:8080: the shop, the admin panel and the invoicing. Changing the invoice layout means building and deploying the entire application, but you can also follow any bug from controller to database in one debugging session.
Our own explanation, not a quote from the book.
In the book
Sentences from The Software Realm, Decoded that mention Monolith, exactly as printed.
2 more passages about Monolith in the full book
Read every conversation where Monolith comes up, with the interactive slides and demos.
Where it fits
Startups, smaller applications, MVPs
Coverage in the book
Explained and compared with alternatives, so you know where and why it’s used.
