How deeply does Think Like a CTO cover monolithic architecture?

Defines coupling and deployment shape, then stops at an executive-level comparison and yes-or-no checklist.

Monolithic architecture

A monolithic architecture packages an application or substantial part of an enterprise as a single tightly coupled deployable unit.

Monolithic architecture packages an enterprise or substantial part of it as one deployable unit: typically a single tightly coupled codebase, compiled and released together. It remains common in legacy enterprises, although many organizations use hybrid designs alongside microservices. section 8.6

Recognize a likely monolithic architecture when several of these conditions apply:

A single codebase contains the system, with no internal libraries. section 8.6
One database drives all systems. section 8.6
An outage stops the entire system from delivering. section 8.6
The architecture depends on a single server or requires planned outages for upgrades. section 8.6

Proof-of-concept use

Monolithic architecture still has a place in proof-of-concept projects, where a single deployable unit can support an initial enterprise solution before later architectural decisions are made. section 8.9

Table 8.4 Microservices vs. monolithic checklist (view table figure)

Single code base, with no internal libraries.	Yes / No
Single database that drives all systems.	Yes / No
An outage causes everything to stop delivering.	Yes / No
Single-server architecture.	Yes / No
Upgrading software requires a planned outage.	Yes / No

Use the checklist to assess whether a system exhibits the main structural and operational characteristics of monolithic architecture. section 8.6

How Think Like a CTO covers it

liveBook manning.com

Read Think Like a CTO on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Google Anthos in ActionA monolithic application is an application whose major capabilities are implemented and deployed as one largely indivisible unit.
liveBook manning.com

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformAn application whose functionality is implemented in a single large service rather than multiple independently deployable services.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformAn infrastructure-as-code organization pattern in which all infrastructure resources are defined in one tightly coupled configuration.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureA monolithic application is a software application whose major functionality is deployed as a single unit.
liveBook manning.com

Platform Engineering on KubernetesA monolithic application packages its major functionality into a single deployable software unit.
liveBook manning.com

Software Security for DevelopersA monolith, or monolithic application, is an application architecture in which the system's components run within one codebase, process, or deployable unit.
liveBook manning.com

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.

Compare how 8 books explain monolithic architecture →

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.

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.