Potholes in the road from monolithic hell: Microservices adoption anti-patterns

Last week, I had the pleasure of giving a keynote at O’Reilly’s excellent software architecture conference in London. The talk covers several anti-patterns of microservices adoption that I’ve observed while working with clients around the world.

The anti-patterns

The anti-patterns are:

Microservices are a magic pixie dust - believing that a sprinkle of microservices will solve all of your development problems
Microservices as the goal - making the adoption of microservices the goal and measuring success in terms of the number of services written
Scattershot adoption - multiple application development teams attempt to adopt the microservice architecture without any coordination
Trying to fly before you can walk - attempting to adopt the microservice architecture (an advanced technique) without (or not committing to) practicing basic software development techniques, such as clean code, good design, and automated testing
Focussing on Technology - focussing on technology aspects of microservices, most commonly the deployment infrastructure, and neglecting key issues, such as service decomposition
More the merrier - intentionally creating a very fine-grained microservice architecture
Red Flag Law - retaining the same development process and organization structure that were used when developing monolithic applications.

Slides

Chris Richardson details several anti-patterns of microservices adoption that he’s observed while working with clients around the world. You’ll learn the challenges that enterprises often face and how to overcome them as well as how to avoid the potholes when escaping monolithic hell.

OReilly SACON London: Potholes in the road from monolithic hell: Microservices adoption anti-patterns from Chris Richardson