Monolith
An application whose core is deployed as one unit; clear internal modules are still possible.
Deploy together
A monolith is an application whose core is deployed as a single unit. It may contain multiple business areas and clearly separated modules. An external database or use of other services does not contradict the term.
In a fictional example, quote management and order processing are released as one application. A change to the quote module therefore enters the same deployment. This can simplify coordination, but requires suitable checks for affected parts. Monolith means neither one source file nor inevitably disorganised code. Suitability depends on change needs, workload, failure requirements and operations; the label alone does not assess quality.
Sources
Related terms
- Software architectureFundamental decisions about a software system’s structure, interactions and quality goals.
- MicroservicesAn architecture of bounded services intended to evolve, operate and deploy as independently as practical.
- Modular monolithAn application deployed together with explicitly bounded internal modules and interfaces.
- Cache stampedeA cache stampede occurs when concurrent cache misses trigger the same expensive calculation or data query repeatedly.
- BackpressureBackpressure adjusts incoming data to the receiver’s processing capacity through signals to slow down or pause.
- Race conditionA result depends on the timing of overlapping accesses and can therefore be wrong.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.