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?

Apr 25, 2025 · I’ll compare and contrast implementing complex authorization requirements within the individual microservices versus using a dedicated authorization service, such as Oso Cloud.

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.

Today, he is a recognized thought leader in microservices and speaks regularly at international conferences. Chris is the author of the book Microservice Patterns. Chris helps organizations …

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 …

The granularity of APIs provided by microservices is often different than what a client needs. Microservices typically provide fine-grained APIs, which means that clients need to interact with …

Create a microservice chassis framework that can be foundation for developing your microservices. The chassis implements Reusable build logic that builds, and tests a service. This includes, for example, …

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?