Talk:Monolithic application

	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.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Very low quality article edit

Latest comment: 7 months ago1 comment1 person in discussion

The article lacks proper references and has a down view of the concept instead of explaining what it is. The article is also very focused on explaining what modules are and why they are good, getting out of the topic. I would go a step forward and say that this article has wrong information.

Edit: Please elaborate which information is wrong. — Preceding unsigned comment added by Redyaung2003 (talk • contribs) 18:14, 11 October 2023 (UTC)Reply

Single-tiered edit

Latest comment: 8 years ago2 comments2 people in discussion

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)Reply

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.
— http://martinfowler.com/articles/microservices.html

}

Also consider this pattern description on Microservice.io:

The application has either a layered or hexagonal architecture and consists of different types of components
— http://microservices.io/patterns/monolithic.html

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

References

^ 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.

External links modified (February 2018) edit

Latest comment: 6 years ago1 comment1 person in discussion

Hello fellow Wikipedians,

I have just modified one external link on Monolithic application. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 18:32, 4 February 2018 (UTC)Reply

Re: "Modularity" edit

Latest comment: 6 years ago1 comment1 person in discussion

The claim that traditional ("monolithic") applications lack modularity sounds like sales-talk and painting with too wide a brush. Classes, methods, functions, etc. are tools of mudularity they usually have. What they may lack is "inter-application" modularity. It's roughly comparable to claiming I am not "friendly" because I am not friendly to my neighbors. However, I may still be friendly to relatives and co-workers.

Related, there are trade-offs to increasing inter-application modularity: it's rarely a free lunch, as implied. Inter-application modularity is not a new concept nor new technology. Using it is a matter of balancing engineering and support trade-offs. — Preceding unsigned comment added by 146.233.255.211 (talk) 18:12, 5 March 2018 (UTC)Reply

Add topic

[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.

[1]