You are receiving this email because you subscribed to the microservices.io mailing list.

Helping organizations accelerate software delivery

You are eager to accelerate development to keep up with evolving business needs

You suspect that you have outgrown your monolith and need a more nimble architecture

You have adopted microservices and want simpler and faster software delivery

I provide consulting and training services that help organizations improve their architecture and accelerate software delivery.

I can, for example, review your microservice architecture and identify areas of improvement, or teach a workshop on how to design a microservice architecture.

I also can teach a 1 day workshop Microservices rules: what good looks like that can help you decide whether microservices are a good fit for your application.

Another option, is my Architecting for fast, sustainable flow workshop that will teach you how to architect for fast flow including how to choose between the monolith and microservice architectures.

I’ve scheduled two public Architecting for fast, sustainable flow - Enabling DevOps and Team Topologies thru architecture workshops in September:

• Americas, 8am-11am Pacific Time, September 4th-6th, 2024
• World, 9am-11am CET/4pm-7pm Korea Time, September 16th-18th, 2024

To learn more, please see the workshop description.

Recently, I gave this presentation at a company’s internal meetup. It’s the latest version of my Microservices Rules talk.

These 11 rules are a great checklist that engineering leaders can use to assess the state of their organization, its delivery practices and its application’s architecture.

To learn more, please read the article.

In November, I’ll be in Berlin and Milan for workshops and talks. If you need workshops or consulting at your company, please don't hesitate to contact me.

Learn more.

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.

Read more or enroll in my bootcamp!