Microservice architecture

As explained in Google Anthos in Action

A microservices architecture structures an application as independently deployable services that communicate over a network.

Microservice architecture structures an application as independently evolvable services that communicate over a network. Services separate business concerns, establish contracts, and can be updated, scaled, replaced, scheduled, or debugged independently. This supports frequent delivery on distributed infrastructure rather than tightly coupled monolithic releases. section 1.1 section 16.0

A production microservice architecture trades monolithic simplicity for independent service operations:

• Decouple business logic into self-contained services so teams can accelerate development and optimize individual components. section 16.3
• Manage added configuration, deployment, maintenance, and dependency complexity across many environments. section 16.3
• Use automation and configuration as code to deploy the whole application consistently across public clouds and on-premises data centers. section 16.3
• Use a service mesh to resolve logical service dependencies, enforce security policy and mutual TLS, connect traditional VMs, and observe performance. section 16.3
• Prefer incremental modernization: containerize existing applications first, then refactor selected components instead of requiring a big-bang rewrite. section 15.3.4 section 16.6

Modernization path

A modern application can be containerized, integrated with CI/CD, and run on Anthos before further refactoring into microservices. A traditional Linux or Windows monolith can be containerized with Migrate for Anthos; applications requiring legacy drivers can move to bare metal or Google Cloud VMware Engine and be refactored later. section 15.3.4

Figure 15.3 A complete modernization journey

Use the modernization journey to compare containerization, Anthos deployment, direct VM migration, and later microservice refactoring. section 15.3.4

How Google Anthos in Action covers it

How deep it goes

Explains modularity, deployment benefits, operational drawbacks, service-mesh capabilities, and incremental migration, but not service implementation code.

Examples

Uses Anthos deployments, containerized Linux or Windows applications, Migrate for Anthos, VM migration, mutual TLS, and service-level objectives.

What it assumes

Assumes familiarity with applications and distributed infrastructure while teaching the shift from tightly coupled monoliths to modular services.

What you can do after

Operate/configure microservice applications with automated deployment, service-mesh security, dependency management, and performance observability.

How it connects

Connects microservices with monoliths, containers, CI/CD, cloud native development, service meshes, Anthos, security, 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 architectural style that structures an application as a collection of small, independently deployable services with distinct boundaries.
• 

  liveBookmanning.com
  gRPC Microservices in GoMicroservice architecture is an architectural style that structures an application as loosely coupled, independently deployable, and independently scalable services.
• 

  liveBookmanning.com
  Cloud Observability in ActionA microservices application is an application composed of independently deployable services that communicate over interfaces.
• 

  liveBookmanning.com
  Think Like a CTOA microservices architecture structures a system as independently deployable services that are narrowly scoped and communicate through defined interfaces.
• 

  liveBookmanning.com
  AI Agents in Action, Second EditionA microservices architecture is a software architecture in which an application is composed of independently deployable services with focused responsibilities.
• 

  liveBookmanning.com
  Go in Practice, Second EditionA microservice architecture is an application architecture composed of independently deployable services that communicate over a network.
• 

  liveBookmanning.com
  Software Security for DevelopersA software architecture that decomposes an application into independently deployable services organized around business capabilities.
• 

  liveBookmanning.com
  Kubernetes for DevelopersMicroservices is an architectural pattern that structures an application as multiple independently maintained services.
• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionA microservice architecture structures an application as multiple independently deployable services that collaborate through defined interfaces.
• 

  liveBookmanning.com
  Kafka for ArchitectsMicroservices architecture is an architectural style composed of independently deployable services organized around separate capabilities.
• 

  liveBookmanning.com
  Python Concurrency with asyncioMicroservice architecture is a system design style that structures an application as a set of independently deployable services communicating over defined interfaces.
• 

  liveBookmanning.com
  BDD in Action, Second EditionMicroservice architecture is an application architecture in which independently deployable services implement separate business capabilities and communicate through defined interfaces.
• 

  liveBookmanning.com
  Authorization in ActionMicroservices is an architectural pattern in which an application is composed of independently deployable services that communicate over a network.

Compare how 14 books explain microservice architecture →

Related concepts

• monolithic architecturealternative to · Monolithic architecture is a software architecture in which an application's major functionality is organized and deployed as a single integrated unit.
• distributed systemkind of · A distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
• autonomyproduces · Autonomy is the capacity or degree to make decisions and act independently within a defined responsibility or set of limits.
• servicehas part · A service is a capability or activity provided by an entity to meet the needs of users or other components.
• fast flowproduces · Fast flow is the rapid, sustainable movement of work through a value stream, supported by minimal delays and timely feedback.

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.