Monolithic application: Difference between revisions

Revision as of 14:04, 28 November 2019

Revision as of 10:57, 17 September 2020

Line 1:

In [[software engineering]], a '''monolithic application''' describes a single-tiered [[Application software|software application]] in which the [[user interface]] and data access code are combined into a single program from a single [[Platform (computing)|platform]].

A monolithic application is self-contained, and independent from other computing applications. The design philosophy is that the application is responsible not just for a particular task, but can perform every step needed to complete a particular function.<ref>ICCI [http://www.codingthearchitecture.com/2014/11/19/what_is_a_monolith.html Monolithic Applications] Retrieved on 5 August 2007</ref><ref>Information Technology Services [http://www.its.state.nc.us/Information/Glossary/glossm.asp Monolithic Application] {{webarchive|url=https://web.archive.org/web/20070902151937/http://www.its.state.nc.us/Information/Glossary/Glossm.asp |date=2007-09-02 }} Retrieved on 28 November 2019</ref> Today, some personal finance applications are monolithic in the sense that they help the user carry out a complete task, end to end, and are [[Information_silo|private data silos]] rather than parts of a larger system of applications that work together. Some [[word processor]]s are monolithic applications.<ref>Microsoft [http://msdn2.microsoft.com/en-us/library/aa480455.aspx Three-tier Application] Retrieved on 3 August 2007</ref> These applications are sometimes associated with [[mainframe computers]].

In software engineering, a monolithic application describes a software application which is designed without modularity. Modularity is desirable, in general, as it supports reuse of parts of the application logic and also facilitates maintenance by allowing repair or replacement of parts of the application without requiring wholesale replacement.