Metraipolis › archive › dc_a012e7ed9710

Monolithic application — Wikipedia (en)

Source
Wikipedia (en)
Original
https://en.wikipedia.org/wiki/Monolithic_application
License (as archived)
CC-BY-SA-4.0
Archived
2026-10-06T00:01:02.002Z
SHA-256 of the archived text
4a3ad9ea1afb03af643881571b568116d32c0f8cd5bea5a8a0c736c706ed2379
Stable URL of this page
https://metraipolis.com/documento/dc_a012e7ed9710

How to cite

Monolithic application — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Monolithic_application (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_a012e7ed9710 (Metraipolis archive dc_a012e7ed9710, sha256 4a3ad9ea1afb03af643881571b568116d32c0f8cd5bea5a8a0c736c706ed2379)
BibTeX
@misc{dca012e7ed9710,
  title = {Monolithic application — Wikipedia (en)},
  howpublished = {Wikipedia (en)},
  url = {https://en.wikipedia.org/wiki/Monolithic_application},
  note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_a012e7ed9710; sha256 4a3ad9ea1afb03af643881571b568116d32c0f8cd5bea5a8a0c736c706ed2379},
  year = {2026}
}

Archived text

Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Monolithic_application. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

In software engineering, a monolithic application is a single unified software application that is self-contained and independent from other applications, but typically lacks flexibility. There are advantages and disadvantages of building applications in a monolithic style of software architecture, depending on requirements. Monolith applications are relatively simple and have a low cost but their shortcomings are lack of elasticity, fault tolerance and scalability. Alternative styles to monolithic applications include multitier architectures, distributed computing and microservices. Despite their popularity in recent years, monolithic applications are still a good choice for applications with small team and little complexity. However, once it becomes too complex, you can consider refactoring it into microservices or a distributed application. Note that a monolithic application deployed on a single machine, may be performant enough for your current workload but it's less available, less durable, less changeable, less fine-tuned and less scalable than a well designed distributed system. 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. Some personal finance applications are monolithic in the sense that they help the user carry out a complete task, end to end, and are private data silos rather than parts of a larger system of applications that work together. Some word processors are monolithic applications. These applications are sometimes associated with mainframe computers. In software engineering, a monolithic application describes a software application that is designed as a single service. Multiple services can be desirable in certain scenarios as it can facilitate maintenance by allowing repair or replacement of parts of the application without requiring wholesale replacement. Modularity is achieved to various extents by different modular programming approaches. Code-based modularity allows developers to reuse and repair parts of the application, but development tools are required to perform these maintenance functions (e.g. the application may need to be recompiled). Object-based modularity provides the application as a collection of separate executable files that may be independently maintained and replaced without redeploying the entire application (e.g. Microsoft's Dynamic-link library (DLL); Sun/UNIX shared object files). Some object messaging capabilities allow object-based applications to be distributed across multiple computers (e.g. Microsoft's Component Object Model (COM)). Service-oriented architectures use specific communication standards/protocols to communicate between modules. In its original use, the term "monolithic" described enormous mainframe applications with no usable modularity. This, in combination with the rapid increase in computational power and therefore rapid increase in the complexity of the problems wh

Tema degli esploratori: calcolo e infrastrutture (deposito sistematico; ricerca «distributed computing»).
Fonte: Wikipedia in inglese, voce «Monolithic application» — https://en.wikipedia.org/wiki/Monolithic_application
Wikidata Q6901701: «type of software architectural system design.» (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q6901701
Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Monolithic_application?action=history).
Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza.
Estratto dell'introduzione non modificato nel contenuto; revisione 1337656364, consultata il 2026-10-05T23:25:47.216Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: bb289aaf3eb3783a81a40a38f888e503ecd77f0bf8ca2c34986350aceeabdcfb