Dark matter force: simple interactions

microservice architecture   architecting   dark energy and dark matter  

a dark energy, dark matter force

An operation’s complexity is proportional to the number of components that collaborate to implement it and the number of messages they exchange. Let’s look at why simple interactions are important and how minimizing their complexity is an attractive force between subdomains.

Ideally each operation should be local to a single service

Ideally, an operation should be local to a single service. That’s because a local operation is easier to understand and troubleshoot. If an operation fails, you know exactly which service is responsible. You only need to look in the logs of that service. The knowledge about that service often belongs to a single team.

But it’s inevitable that some operations will be distributed

However, it’s not always possible to create a microservice architecture where all operations are local. It would require each operation’s subdomains to be packaged as a single service, which might only be achieved by a monolith. As a result, some operations will be distributed across multiple services. Each distributed operation is implemented by multiple collaborating services.

Simplify critical operations

When designing a microservice architecture, you should strive to group the subdomains so that the critical operations are as simple as possible. For example, business critical operations that need to be highly available should either be local to a single service or be distributed across as few services as possible in order to minimize the amount of time it takes to troubleshoot a failure.


microservice architecture   architecting   dark energy and dark matter  


Copyright © 2024 Chris Richardson • All rights reserved • Supported by Kong.

About Microservices.io

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.

New workshop: Architecting for fast, sustainable flow

Enabling DevOps and Team Topologies thru architecture

DevOps and Team topologies are vital for delivering the fast flow of changes that modern businesses need.

But they are insufficient. You also need an application architecture that supports fast, sustainable flow.

Learn more and register for my June 2024 online workshops....

NEED HELP?

I help organizations improve agility and competitiveness through better software architecture.

Learn more about my consulting engagements, and training workshops.

LEARN about microservices

Chris offers numerous other resources for learning the microservice architecture.

Get the book: Microservices Patterns

Read Chris Richardson's book:

Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code

Virtual bootcamp: Distributed data patterns in a microservice architecture

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 ILFJODYS to sign up for $95 (valid until April 12, 2024). There are deeper discounts for buying multiple seats.

Learn more

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

Signup for the newsletter


BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,


The Eventuate platform

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.


Join the microservices google group