What are the defining characteristics of a monolithic architecture?

1 Single codebase

One of the main features of a monolithic architecture is that the application has a single codebase, which contains all the business logic, user interface, database access, and other functionalities. This means that the developers work on the same codebase and share the same resources, such as libraries, frameworks, and tools. The codebase is usually organized into modules or layers, but they are not independent or reusable.

2 Single deployment

Another characteristic of a monolithic architecture is that the application is deployed as a single unit, usually as a single executable or a single archive file. This means that the deployment process is simple and straightforward, as there is no need to coordinate multiple components or services. However, it also means that any change in the codebase requires a full redeployment of the application, which can be time-consuming and risky.

3 Single point of failure

A third characteristic of a monolithic architecture is that the application is vulnerable to a single point of failure, which means that any error or issue in one component can affect the whole system. This can lead to poor reliability, availability, and performance, as the application cannot scale or recover easily. Moreover, it can make the application harder to test, debug, and maintain, as the codebase grows in size and complexity.

4 Single technology stack

A fourth characteristic of a monolithic architecture is that the application is built using a single technology stack, which means that the developers use the same programming language, framework, platform, and tools for the entire application. This can have some benefits, such as reducing the learning curve, the compatibility issues, and the operational costs. However, it can also limit the flexibility, the innovation, and the adaptability of the application, as it cannot leverage new or different technologies.

5 Single team

A fifth characteristic of a monolithic architecture is that the application is developed by a single team, which means that the developers have a shared vision, a common understanding, and a close collaboration. This can foster a high cohesion, a low coupling, and a consistent quality of the codebase. However, it can also create some challenges, such as increasing the communication overhead, the coordination cost, and the dependency among the developers.

6 Single responsibility

A sixth characteristic of a monolithic architecture is that the application has a single responsibility, which means that it fulfills a specific and well-defined purpose or function. This can make the application easy to understand, to design, and to use. However, it can also make the application rigid, inflexible, and hard to evolve, as it cannot accommodate new or changing requirements, features, or functionalities.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?