Microservices Rules 7 Design Loosely Design Time Coupled

The microservices pattern language is your guide when designing an architecture: service collaboration, testing, deployment, common crosscutting concerns and more.

I appreciate how you highlighted the benefits of microservices, such as increased scalability and faster development cycles, while also addressing the potential challenges involved. Your practical …

Hi there! I'm looking to learn how to build multi-tenant microservices. Can you recommend some resources?

Write some code - Use the Eventuate.io platform with popular frameworks, such as Spring Boot to tackle distributed data management challenges in your microservices architecture.

In a portfolio of hundreds of microservices with dozens of key biz transactions each with 3-5 participating services, how to make sure sagas are implemented properly across all service teams? has anyone …

Several microservices maintaining connection pools to the same database creates contention. Multiple independent processes accessing the database via some ORM layer can cause hard to diagnose …

Using this pattern and thinking in microservices, once each service has its own database, should I have an Outbox table in each service database or should I have a common (centralized) database/service?

The Domain-specific protocol pattern is an alternative pattern The RPI pattern is an alternative pattern See also My book Microservices patterns describes inter-communication in depth Enterprise …

May 20, 2025 · This is another article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively.

The Microservices Example application is an example of an application that uses client-side service discovery. It is written in Scala and uses Spring Boot and Spring Cloud as the Microservice chassis.