liveBook · Manning

Infrastructure coupling

As explained in Microservices Patterns, Second Edition

Infrastructure coupling is a dependency in which services are affected by shared deployment infrastructure, infrastructure resources, or infrastructure configuration changes.

Infrastructure coupling occurs when components share infrastructure and one component’s behavior affects another. They need not communicate directly: shared compute, networking, databases, or message brokers can link their runtime behavior. section 4.5

Shared infrastructure creates two main risks:

  • Resource competition: one service can consume network bandwidth or database capacity, issue expensive queries, or hold locks that block another service. section 4.5.2
  • Configuration changes made to support one service can unintentionally affect another service using the same infrastructure. section 4.5.2

Customer Service and Order Service

When both services share a Kubernetes cluster and database server, the less critical Customer Service could impair the more critical Order Service through resource competition or infrastructure changes. section 4.5.1

For highly available services, combine runtime decoupling with dedicated infrastructure and infrastructure services. A separate cluster and database for the Order Service reduce resource sharing and exposure to changes made for other services. Some coupling is inevitable, so weigh isolation against its drawbacks. section 4.5.3 section 4.6

Figure 4.17 To minimize infrastructure coupling and improve availability, services that are critical to the business should be deployed on separate infrastructure and loosely runtime coupled to the rest of the application
infrastructure coupling decoupled

Shows how separate infrastructure and loose runtime coupling protect critical services. section 4.5.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines shared-infrastructure effects, distinguishes resource competition from configuration side effects, and gives isolation strategies.
Examples
Uses Customer Service and Order Service sharing a Kubernetes cluster and database, then separates the critical Order Service.
What you can do after
Diagnose how shared resources or configuration changes can impair a service, then isolate critical services on separate infrastructure.
How it connects
Connects infrastructure coupling to runtime coupling, service availability, and resource competition.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.