3 min read

There’s more to a microservice architecture than services

There's more to a microservice architecture than services

From time to time, I encounter organizations who have been struggling with their microservice architecture. Sometimes, the problem is data inconsistencies across services. An update occurs in one service, but a corresponding update doesn’t happen in a related service. It’s as the Order Service fails to notify the Fulfillment Service that the order needs to be shipped. Or, perhaps, the application has poor performance or is brittle with frequent outages. And, the developers are jumping through all kinds of hoops to fix customer problems including manually updating the database.

In this article, I’ll describe one of the main reasons why these problems occur and how to prevent them.

This post is for paying subscribers only