Overview
Direct Answer
Monolithic architecture is a software design pattern where all application components—user interface, business logic, and data access layers—are built, deployed, and scaled as a single, interdependent unit. This contrasts with distributed architectures where functionality is separated into independently deployable services.
How It Works
All application modules reside within a shared codebase and execute within a single process or tightly coupled runtime environment. Changes to any component require recompilation and redeployment of the entire application. Data is typically stored in a centralised database, with all services accessing the same schema, ensuring consistency but creating tight coupling.
Why It Matters
Monolithic designs simplify initial development, deployment, and operational monitoring for small to medium-scale applications, reducing infrastructure complexity and latency between components. However, organisations increasingly question this approach as applications scale, as it can become a bottleneck to development velocity and system resilience.
Common Applications
Traditional enterprise applications such as customer relationship management systems, content management platforms, and financial transaction processing systems have historically used this pattern. Many legacy systems continue operating as monolithic deployments across banking, insurance, and retail sectors.
Key Considerations
Whilst monolithic architecture offers simplicity initially, it creates scalability limitations—teams must scale the entire application rather than individual services. Technology lock-in and difficulty in adopting new frameworks or languages are significant constraints as systems mature.
More in Cloud Computing
Cloud-Native Development
Service ModelsAn approach to building applications that fully exploit cloud computing advantages including microservices, containers, dynamic orchestration, and continuous delivery.
Hypervisor
InfrastructureSoftware that creates and manages virtual machines, allowing multiple operating systems to share a single hardware host.
Spot Instances
Service ModelsSpare cloud computing capacity offered at steep discounts compared to on-demand pricing, available when the provider has excess resources but subject to interruption.
Auto-Scaling
InfrastructureAutomatically adjusting compute resources based on current demand to maintain performance and optimise costs.
Cloud Security
Strategy & EconomicsThe set of policies, technologies, and controls deployed to protect cloud-based systems, data, and infrastructure.
FinOps
Strategy & EconomicsA cultural practice combining technology, finance, and business to manage cloud costs through data-driven decision making.
Software as a Service
Service ModelsCloud computing model that delivers software applications over the internet on a subscription basis.
Reserved Instance
Strategy & EconomicsA cloud pricing model where users commit to a specific resource configuration for a term in exchange for discounted rates.