One of the defining characteristics of the microservice architecture is that services are loosely coupled. Services should ideally be self-contained but some form of inter-service communication is inevitable. You should, however, be very careful about using synchronous calls (e.g. REST or gRPC) between services If you mimic the inter-module communication patterns in your monolithic you are likely to have a very brittle system due to the runtime coupling. To reduce runtime coupling, you should strive to use asynchronous messaging wherever possible.
My favorite book on asynchronous messaging is Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf. I bought it back in 2003, so I guess it’s a classic.
It’s a pattern language and visual notation for messaging systems.
I find it useful to describe an application’s architecture in terms of patterns such as Message Channel rather than immediately leaping into the technical details of today’s fashionable message broker. Later you can map that abstract architecture to an actual implementation. For example, take a look at the diagrams in my posts about orchestration-based and choreography-based sagas, such as the follow:
This is a must read book if you are building applications that use asynchronous messaging. You can learn more about the book and the pattern language on the book’s website.
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 more
Chris 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