How deeply does Think Like a CTO cover microservice architecture?

Defines service scope, communication, and independence, then offers a monolith checklist rather than implementation instructions.

Microservice architecture

As explained in Think Like a CTO

A microservices architecture structures a system as independently deployable services that are narrowly scoped and communicate through defined interfaces.

Microservice architecture divides an enterprise system into small applications, each with a narrow responsibility. Services interact through an API, service bus, or message queue. A strong service has its own data store, execution environment, and release cycle, so it can change without requiring the rest of the system to be released with it. section 8.6

The appeal is lower change risk and the freedom to choose tools suited to each service’s role. Contrast this with a tightly coupled monolith: even a small library upgrade can have unintended effects elsewhere. The choice is not absolute. Enterprises may combine both approaches, and a monolith can still suit a proof of concept. section 8.6 section 8.9

Replacing a legacy language incrementally

If a legacy language needs replacing, look for areas that can be refactored into services. Carving out those areas can avoid a complete rewrite. First weigh the wider technology landscape, including the recruitment market; unfamiliarity with a language alone is not a reason to replace it. section 8.8.1

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 how monolithic the current system is. Three or more yes answers point toward a monolithic architecture; the questions test shared code and data, outage scope, server structure, and upgrade downtime. 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

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.
liveBook manning.com

Google Anthos in ActionA microservices architecture structures an application as independently deployable services that communicate over a network.
liveBook manning.com

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

Cloud Observability in ActionA microservices application is an application composed of independently deployable services that communicate over interfaces.
liveBook manning.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.
liveBook manning.com

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

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

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

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

Kafka for ArchitectsMicroservices architecture is an architectural style composed of independently deployable services organized around separate capabilities.
liveBook manning.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.
liveBook manning.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.
liveBook manning.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 Think Like a CTO. The section links point to the parts of the book it draws on.