Monolithic architecture

As explained in Google Anthos in Action

A monolithic application is an application whose major capabilities are implemented and deployed as one largely indivisible unit.

A monolithic application keeps its functions tightly coupled. That contrasts with a microservices architecture, where services can be updated, scaled, replaced, and debugged independently. A monolith can still be a candidate for containerization; moving it into a container does not, by itself, split it into services. section 1.1 section 15.3.4

A three-tier Java application

A traditional three-tier Java application is one example of a monolith. If it runs on WebSphere or WebLogic, inspect its use of proprietary server features before considering a move to an open source server such as Tomcat or JBoss. That deployment change is distinct from a later redesign into microservices. section 16.2.1

Modernize incrementally while keeping the existing application running:

• Improve development and deployment first, including suitable language or framework changes. section 16.1
• Containerize suitable workloads with Migrate for Anthos, then add continuous integration, automated testing, continuous deployment, and observability. section 16.1
• Refactor toward microservices when ready. Workloads needing particular drivers or legacy support may instead move as VMs before later refactoring. section 16.2.1 section 15.3.4

Figure 16.6 Monolith vs. microservice architecture

Compare the monolith and microservice architecture diagrams when deciding which changes alter deployment and which change the application’s structure. section 16.2.1

How Google Anthos in Action covers it

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 it assumes

Introduces the monolith through coupled functions while treating VMs, containers, and CI/CD as deployment concepts.

What you can do after

Practice/perform incremental modernization by containerizing suitable workloads, improving delivery and observability, and planning later microservice refactoring.

How it connects

Connects monolithic architecture to microservices, containerization, continuous integration, continuous deployment, and observability.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.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.
• 

  liveBookmanning.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.
• 

  liveBookmanning.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.
• 

  liveBookmanning.com
  Think Like a CTOA monolithic architecture packages an application or substantial part of an enterprise as a single tightly coupled deployable unit.
• 

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

  liveBookmanning.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.
• 

  liveBookmanning.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 Google Anthos in Action. The section links point to the parts of the book it draws on.