
What are microservices?
The microservices pattern language is your guide when designing an architecture: service collaboration, testing, deployment, common crosscutting concerns and more.
Microservices Pattern: Microservice Architecture pattern
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 …
Adopt the Microservice Architecture
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.
A pattern language for microservices
Hi there! I'm looking to learn how to build multi-tenant microservices. Can you recommend some resources?
Pattern: API Gateway / Backends for Frontends - Microservices
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 …
Microservices rules #8: Design independently deployable services
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.
Pattern: Messaging - Microservices
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 …
Pattern: Saga - Microservices
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 …
Berlin meetup: Microservices rules - what good looks like
Nov 29, 2025 · Sadly, however, microservices have often been widely misunderstood and used inappropriately. As a result, many organizations have struggled to benefit from their adoption.
Pattern: Transactional outbox - Microservices
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?