Monolithic architecture
Monolithic architecture is a software architecture in which an application's major functionality is organized and deployed as a single integrated unit.
Google Anthos in Action
A monolithic application is an application whose major capabilities are implemented and deployed as one largely indivisible unit.
- How it is used
- Frames tightly coupled application functions as a starting point for incremental modernization toward microservices.
- How deep it goes
- Defines the pattern through tight coupling and illustrates it with three-tier Java, then develops migration steps rather than monolith internals.
- Examples
- Uses a three-tier Java application and a conditional WebSphere-to-Tomcat move to illustrate deployment choices.
- What you can do after
- Practice/perform incremental modernization by containerizing suitable workloads, improving delivery and observability, and planning later microservice refactoring.
Read how Google Anthos in Action explains monolithic architecture →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
An application whose functionality is implemented in a single large service rather than multiple independently deployable services.
- How it is used
- Serves as a simpler starting architecture and a practical comparison point when choosing or moving toward microservices.
- How deep it goes
- Defines a monolith as a single-process application, weighs its trade-offs, and outlines iterative conversion without prescribing a universal migration plan.
- Examples
- Compares monolithic and microservices versions of a video-streaming application and considers prototypes, small applications, and hybrid arrangements.
- What you can do after
- Evaluate/understand when a monolith fits and why migration should proceed through small, tested changes.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
An infrastructure-as-code organization pattern in which all infrastructure resources are defined in one tightly coupled configuration.
- How it is used
- Uses refactoring to reduce team conflicts, deployment delays, and tightly coupled infrastructure changes.
- How deep it goes
- Defines the pattern and details a staged extraction workflow, stopping short of prescribing one universal module structure.
- Examples
- Uses GCP IAM policies, service accounts, networks, subnets, and a container orchestrator as extraction examples.
- What you can do after
- Apply it via Terraform and provider APIs to separate resources, import existing state, inject dependencies, and verify no unintended changes.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A monolithic application is a software application whose major functionality is deployed as a single unit.
- How it is used
- Uses monolithic architecture to diagnose when deployment, integration, and team coordination impede business goals.
- How deep it goes
- Explains deployment and organizational consequences through industry cases, stopping short of code-level refactoring instructions.
- Examples
- Uses an airline’s whole-system deployments, Vinted’s shared codebase, and acquired legacy systems to show different pressures.
- What you can do after
- Evaluate/understand when a monolith warrants boundary discovery and architectural change aligned with business needs.
Think Like a CTO
A monolithic architecture packages an application or substantial part of an enterprise as a single tightly coupled deployable unit.
- How it is used
- Frames enterprise technology decisions by contrasting a single deployable unit with microservices.
- How deep it goes
- Defines coupling and deployment shape, then stops at an executive-level comparison and yes-or-no checklist.
- Examples
- Uses a five-question checklist and proof-of-concept projects as concrete ways to recognize or apply the pattern.
- What you can do after
- Evaluate monolithic architecture by applying a five-question checklist and comparing its change risk with microservices.
Read how Think Like a CTO explains monolithic architecture →
Platform Engineering on Kubernetes
A monolithic application packages its major functionality into a single deployable software unit.
- How it is used
- Frames architectural trade-offs between a shared deployable application and independently evolving services.
- How deep it goes
- Compares code organization, team coordination, integration, and scaling, but does not detail implementation internals.
- Examples
- Uses the Conference application, its home page, back office, and call-for-proposals functionality as bundled use cases.
- What you can do after
- Evaluate when shared deployment and coordination costs make a distributed service design preferable.
Read how Platform Engineering on Kubernetes explains monolithic architecture →
Software Security for Developers
A monolith, or monolithic application, is an application architecture in which the system's components run within one codebase, process, or deployable unit.
- How it is used
- Centralizes application behavior and authorization decisions within one deployable unit.
- How deep it goes
- Explains authorization models, failure modes, and modular boundaries, but stops short of deployment or implementation details.
- Examples
- Uses role checks, department-to-invoice comparisons, and ownership or membership relationships as authorization examples.
- What you can do after
- Apply RBAC, ABAC, or ReBAC using shared user, resource, and relationship data.
Read how Software Security for Developers explains monolithic architecture →
Build Financial Software with Generative AI (From Scratch)
Monolithic architecture is an architectural style in which an application’s functionality is packaged and deployed as a single unit.
- How it is used
- Uses a single deployable package for practical delivery, especially during proof-of-concept development.
- How deep it goes
- Defines the packaging approach and decision rationale but stops short of implementation or internal structure.
- Examples
- Uses a bundled proof-of-concept application and an ACH system overview as concrete references.
- What you can do after
- Evaluate whether an existing monolith needs architectural change by weighing project problems, team experience, size, and risk.
Related concepts
- microservice architecturealternative to · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
- single-process systemkind of · A single-process system is a software system whose execution takes place within one operating-system process.
- distributed systemcontrasts with · A distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
- big ball of mud architectureproduces · Big ball of mud architecture is a software architecture with tangled dependencies, blurred boundaries, and weak structure that make it difficult to understand, maintain, or change.
- databaseuses · A database is an organized collection of persistent data managed by software for storage, retrieval, querying, and modification.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.