Anti-pattern: microservices as the goal

microservices adoption   anti-patterns   software delivery metrics  

New public workshop: Architecting for fast, sustainable flow - enabling DevOps and Team Topologies thru architecture. Learn more and enroll.

In a previous post, I described the Microservices are a magic pixie dust anti-pattern. Another anti-pattern that I’ve observed is an organization making the adoption of microservices the goal. An executive might, for example, announce a microservices transformation initiative and expect every development team to “do microservices”. Development teams then scramble to “do microservices”. Perhaps, a team’s annual or quarterly bonus is affected by how well they “do microservices”. In an extreme case, it might be depend on how many microservices they have deployed.


On the one hand, adopting microservices is a major undertaking and high-level support is essential. But on the other hand, the problem with making microservices the goal is that it ignores other obstacles to rapid, frequent and reliable software delivery including:

  • Inefficient processes and practices - waterfall process, manual testing, manual deployment
  • Silo’d organization - e.g. development hands off code to QA for testing.
  • Poor software quality - the application is a big ball of mud, the code is anything but clean, etc.

An organization that suffers from these problems might not benefit from adopting microservices. It might even make things worse. Also, requiring a team to adoption microservices, risk imposing an architecture on a development team even when it does not make sense for their application.

A better approach

A much better goal is to increase the velocity, frequency and reliability of software delivery. Specific, there are four key metrics to track and improve:

  • Lead time - time from commit to deploy
  • Deployment frequency - number of deploys per day per developer
  • Failure rate - how often deployments fail
  • Recovery time - time to recover from an outage

Each application development team is then responsible for improving these metrics for their application. Sometimes the microservice architecture plays a key role in improving this metrics. But there are other things that can be done to improve these metrics. For example,

microservices adoption   anti-patterns   software delivery metrics  

Copyright © 2024 Chris Richardson • All rights reserved • Supported by Kong.

About is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original, and the author of Microservices patterns.

New workshop: Architecting for fast, sustainable flow

Enabling DevOps and Team Topologies thru architecture

DevOps and Team topologies are vital for delivering the fast flow of changes that modern businesses need.

But they are insufficient. You also need an application architecture that supports fast, sustainable flow.

Learn more and register for my September 2024 online workshops....


I help organizations improve agility and competitiveness through better software architecture.

Learn more about my consulting engagements, and training workshops.

LEARN about microservices

Chris offers numerous other resources for learning the microservice architecture.

Get the book: Microservices Patterns

Read Chris Richardson's book:

Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code

Virtual bootcamp: Distributed data patterns in a microservice architecture

My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!

It covers the key distributed data management patterns including Saga, API Composition, and CQRS.

It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.

The regular price is $395/person but use coupon WURMXAJV to sign up for $95 (valid until July 19th, 2024). There are deeper discounts for buying multiple seats.

Learn more

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

Signup for the newsletter

BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,

The Eventuate platform

Use the platform to tackle distributed data management challenges in your microservices architecture.

Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.

Join the microservices google group