Modular monolith
An application deployed together with explicitly bounded internal modules and interfaces.
Internal boundaries with shared delivery
A modular monolith divides the application core into modules with clear responsibilities and permitted interfaces. The application is still deployed together. One module’s implementation details should not be freely accessible to other modules.
In a fictional example, reports obtain job information through a defined interface instead of directly manipulating internal job tables throughout the application. This boundary must be respected and checked in code and changes; separate folders alone are insufficient. The form can organise internal dependencies, but does not automatically provide independent deployment or failure isolation for every module. Record data ownership, permitted access and checks of module boundaries.
Sources
Related terms
- MonolithAn application whose core is deployed as one unit; clear internal modules are still possible.
- MicroservicesAn architecture of bounded services intended to evolve, operate and deploy as independently as practical.
- 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.
- Memory leakMemory that is no longer needed stays allocated while the program runs.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.