Just a reminder: picking the appropriate architecture for your application is a best practice.

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

As I write in my book, you must pick the architecture that satisfies your application’s non-functional requirements, which are also referred to as CFRs, software quality attributes or -ilities. I’ll give some examples of -ilities shortly.

These days, pro-monolith tweets are guaranteed to have a high level of engagement. The latest was this one:

which was then regurgitated by The New Stack.

The reality is that the Monolithic Architecture and Microservice Architecture are architectural patterns. A pattern is a reusable solution to a problem that occurs in a context. Monolith Always and Microservices Always are mirrors of one another. Neither is a correct except in the sense of a stopped clock. They are both examples of the “Golden Hammer” anti-pattern. Which one you should choose depends on your context, the problem you are trying to solve and the -ilities you need.

In particular, high-performance software delivery, which requires small, autonomous DevOps teams, needs an architecture that is maintainable, testable, deployable, modular and evolvable. Perhaps you can achieve high-performance software delivery of your application using the monolith architecture. That’s especially true for smaller teams and small applications. But many organization have found that they needed the microservice architecture in order to deliver software rapidly, frequently and reliably. Alternatively, perhaps your application’s key -ilities are completely different. For each application, its essential to know your -ilities and choose the appropriate architecture.

And, yes there are anti-patterns of microservice adoption including Magic Pixie Dust and Trying to fly before you can walk.

However, the fact that some organizations adopt microservices for the wrong reasons or implement them incorrectly does not detract from the value of using the microservice architecture right context.

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

About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, 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 Eventuate.io 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