Previously, I wrote how one of the essential characteristic of the microservice architecture is that services are independently deployable. Another essential characteristic is that services are loosely coupled.
There’s actually two different types of coupling:
Minimizing design-time coupling and minimizing runtime coupling are two of the five dark matter forces that shape a microservice architecture.
Let’s look at each type of coupling in turn.
Runtime coupling between services is the degree to which the availability of one service is affected by the availability of another service. Or to be more precise, it’s degree to which the availability of an operation implemented by one service is affected by the availability of another service.
For example, let’s imagine that the createOrder()
system operation is implemented by an HTTP POST /orders
endpoint in the Order Service
.
The Order Service
handles the HTTP POST
by invoking other services, waiting for them to response, and then sending a response to its client.
In this design, the Order Service
cannot respond to the POST
request until the other services respond to it.
The Order Service
(or createOrder()
operation) is said to be runtime coupled to those other services.
As a result, the availability of the createOrder()
operation is reduced since all services must be available.
Minimizing runtime coupling is one of the dark matter attractive forces that resists decomposition. One way to reduce an operation’s runtime coupling is to reduce the number of services that implement it. In fact, we can eliminate runtime coupling entirely by making an operation local to a single service. However, it’s not always possible to create a microservice architecture where all operations are local. That’s likely to violate the dark energy forces, which encourage decomposition.
The other way to reduce runtime coupling while satisfying dark energy forces is to design self-contained services.
A self-contained service responds to a synchronous request with a partial outcome and then asynchronously complete the operation.
For example, the Order Service
could respond to the HTTP POST /orders
request with a 202 Accepted
response and then initiate a Create Order Saga
complete the operation.
This approach improves the availability of the Order Service
.
The drawback is that it makes the client more complex since it must be able to handle partial outcomes and somehow determine the final outcome of the operation.
The degree of design-time coupling between a pair of software elements - classes…services - is the likelihood that they need to change together for the same reason. Design-time coupling between services in a microservice architecture is especially problematic. Let’s look at why it’s a problem and how we can minimize it.
If two services are loosely coupled, then a change to one service rarely requires a change to the other service. However, if two services are tightly coupled, then a change to one service often requires a change to the other service. These types of lock step changes are expensive since it typically involves breaking API changes.
For example, let’s imagine that the Order Service
and Customer Service
are tightly coupled.
Each time a breaking changes needs to be made to the Customer Service
the sequence of steps is as follows:
Customer Service
to add a new major version of its API.
The service must implement both the old and new version of its APIs until all clients have been migrated over.Order Service
to the new API versionCustomer Service
What’s even worse, is that quite often the services are owned by different teams, which requires those teams to coordinate the changes. In other words, design-time coupling between services undermines team autonomy.
Minimizing design-time coupling is one of the dark matter attractive forces that resists decomposition. There are a couple of different ways to minimize design-time coupling between services.
design subdomains to be loosely coupled - loosely coupled subdomains can be packaged as different services. Loose design-time coupling is usually achieved by each subdomain having a stable API that encapsulates its implementation.
package subdomains that are tightly coupled in the same service - If two subdomains are tightly coupled, then packaging them together in the same service will avoid design-time coupling between services.
There are various articles and presentations about loose coupling.
I provide consulting and training.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Learn moreChris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging