Monolithic definition and meaning


You are developing a server-side enterprise application.It must support a variety of different clients including desktop browsers, mobile browsers and native Mobile applications.The application might also expose an API for 3rd parties lớn consume.It might also integrate with other applications via either web services or a message broker.The application handles requests (HTTP.. requests và messages) by executing business logic; accessing a database; exchanging messages with other systems; & returning a HTML/JSON/XML response.There are logical components corresponding to different functional areas of the application.

Bạn đang xem: Monolithic definition and meaning


What’s the application’s deployment architecture?


There is a team of developers working on the application New team members must quickly become productive The application must be easy khổng lồ underst& và modify You want to lớn practice continuous deployment of the application You must run multiple instances of the application on multiple machines in order to satisfy scalability & availability requirements You want to lớn take advantage of emerging technologies (frameworks, programming languages, etc)


Build an application with a monolithic architecture.For example:

a single Java WAR file. a single directory hierarchy of Rails or NodeJS code


Let’s imagine that you are building an e-commerce application that takes orders from customers, verifies inventory & available credit, and ships them.The application consists of several components including the StoreFrontUI, which implements the user interface, along with some backend services for checking credit,maintaining inventory và shipping orders.

The application is deployed as a single monolithic application.For example, a Java web application consists of a single WAR file that runs on a web container such as Tomcat.A Rails application consists of a single directory hierarchy deployed using either, for example, Phusion Passenger on Apache/Nginx or JRuby on Tommèo.You can run multiple instances of the application behind a load balancer in order lớn scale & improve availability.


Resulting context

This solution has a number of benefits:

Simple khổng lồ develop - the goal of current development tools và IDEs is to lớn support the development of monolithic applications Simple to deploy - you simply need lớn deploy the WAR file (or directory hierarchy) on the appropriate runtime Simple khổng lồ scale - you can scale the application by running multiple copies of the application behind a load balancer

However, once the application becomes large và the team grows in kích cỡ, this approach has a number of drawbacks that become increasingly significant:

The large monolithic code base intimidates developers, especially ones who are new khổng lồ the team.The application can be difficult to underst& & modify. As a result, development typically slows down.Also, because there are not hard module boundaries, modularity breaks down over time.Moreover, because it can be difficult khổng lồ understand how khổng lồ correctly implement a change the quality of the code declines over time.It’s a downwards spiral.

Overloaded IDE - the larger the code base the slower the IDE & the less productive sầu developers are.

Overloaded website container - the larger the application the longer it takes khổng lồ start up. This had have a huge impact on developer productivity because of time wasted waiting for the container lớn start. It also impacts deployment too.

Xem thêm: This Man Là Ai Trong Điền Quân, Color Man Là Ai Trong Điền Quân

Continuous deployment is difficult - a large monolithic application is also an obstacle khổng lồ frequent deployments.In order khổng lồ update one component you have to redeploy the entire application.This will interrupt background tasks (e.g. Quartz jobs in a Java application), regardless of whether they are impacted by the change, & possibly cause problems.There is also the chance that components that haven’t been updated will fail to lớn start correctly.As a result, the risk associated with redeployment increases, which discourages frequent updates.This is especially a problem for user interface developers, since they usually need to iterative rapidly và redeploy frequently.

Scaling the application can be difficult - a monolithic architecture is that it can only scale in one dimension. On the one hand, it can scale with an increasing transaction volume by running more copies of the application. Some clouds can even adjust the number of instances dynamically based on load. But on the other hand, this architecture can’t scale with an increasing data volume. Each copy of application instance will access all of the data, which makes caching less effective sầu và increases memory consumption & I/O traffic. Also, different application components have sầu different resource requirements - one might be CPU intensive while another might memory intensive. With a monolithic architecture we cannot scale each component independently

Obstacle to scaling development - A monolithic application is also an obstacle khổng lồ scaling development.Once the application gets lớn a certain kích thước its useful khổng lồ divide up the engineering organization inkhổng lồ teams that focus on specific functional areas.For example, we might want khổng lồ have sầu the UI team, accounting team, inventory team, etc.The trouble with a monolithic application is that it prevents the teams from working independently.The teams must coordinate their development efforts và redeployments.It is much more difficult for a team to lớn make a change and update production.

Requires a long-term commitment to a technology staông chồng - a monolithic architecture forces you khổng lồ be married lớn the technology staông xã (và in some cases, to lớn a particular version of that technology) you chose at the start of development . With a monolithic application, can be difficult to incrementally adopt a newer technology. For example, let’s imagine that you chose the JVM. You have some language choices since as well as Java you can use other JVM languages that inter-operate nicely with Java such as Groovy and Scala. But components written in non-JVM languages vị not have sầu a place within your monolithic architecture. Also, if your application uses a platform framework that subsequently becomes obsolete then it can be challenging to lớn incrementally migrate the application to a newer và better framework. It’s possible that in order to adopt a newer platkhung framework you have sầu to rewrite the entire application, which is a risky undertaking.

Related patterns

The microservice architecture is an alternative sầu pattern that addresses the limitations of the monolithic architecture.

Known uses

Well known internet services such as Netflix, và eBay initially had a monolithic architecture.Most website applications developed by the author had a monolithic architecture.