The Monolith Architecture Pattern

 

• Applications used to be deployed as a single unit where all functionality deployed together inside a single server. We call this architecture approach as Monolithic.

• The most important feature is its have a single supporting database.

Advantages/Pros

• Fewer cross-cutting concerns.
• Simpler development and deployment for smaller teams and applications.
• Better performance due to no network latency.  

Disadvantages/Cons

• Difficult to adopt new technologies.
• Limited agility
• Single code base and difficult to maintain
• Entire code is tightly coupled
• Issues with scalability
• Tiny update and feature development always need a full deployment

various forms of Monolithic with the names like Single-Process Monolith, Modular Monolith and Distributed Monolith

In a monolithic approach, developers work with a single code base, which is then packaged as a unified unit, such as an EAR(Enterprise Archive)/WAR(Web Application Archive) file and deployed in to single web/application server.