Talk:Monolithic application

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Software  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software.
 

Single-tiered[edit]

I'd argue that a monolithic system could be milti-tiered. If each one of those tiers is only used by one higher-level tier and the higher-level tier cannot function without that one-and-only lower-level tier, you have a monolithic system. --PeterRitchie (talk) 17:45, 21 March 2016 (UTC)

There seems to be the need to distinguish between a Monolithic Application and a Monolithic Architecture.

In the context of Microservices there are many references to Monolithic Systems that are layered and component based. Consider this reference from the Microservices page [1] which refers to a "a monolithic, layered system."

Martin Fowler describes the Monolith as usually having three layers:

To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit. Enterprise Applications are often built in three main parts: a client-side user interface (consisting of HTML pages and javascript running in a browser on the user's machine) a database (consisting of many tables inserted into a common, and usually relational, database management system), and a server-side application.

}

Also consider this pattern description on Microservice.io:

The application has either a layered or hexagonal architecture and consists of different types of components

--Ged Byrne —Preceding undated comment added 13:50, 18 April 2016 (UTC)

  1. ^ Miller, Joseph B. (2014). Internet Technologies and Information Services. Library and Information Science Text Series (2 ed.). ABC-CLIO. p. 269. ISBN 9781610698863. Retrieved 2015-08-04. As with many complex information technologies, there are two general architectural options: a monolithic, layered system that embodies all the needed functionalities within one large-scale solution or a modular approach based on microservice architecture (MSA). [...] MSA is a more flexible, modular strategy.