Microservice Architecture
Supported by KongMicroservices adoption anti-pattern: Red flag law
Image from https://www.dedionboutonclub.co.uk
So far in this series I’ve covered the following anti-patterns
- Microservices are a magic pixie dust
- Microservices as the goal
- Scattershot adoption
- Trying to fly before you can walk
- Focussing on Technology
- More the merrier
The final anti-pattern in the series is Red Flag Law. The name is taken from the 19th century Red Flag Traffic Laws that were passed in the US and UK. These laws required a pedestrian to walk in front of each automobile waving a red flag to warn the drivers and riders of horses. As a result, the automobile is forced to travel at the same speed as a pedestrian.
I’ve seen an analogous situation at organizations that adopted the microservice architecture. Despite intending to use microservices to accelerate development, the organization retains the same process and structure that were used when developing monolithic applications. For example, the organization has functional silos, such as separate development and QA teams. It might even have policies that require changes to be pushed to production during a weekend maintenance window.
Consequences
If you don’t change your organization’s software development process and structure, it’s likely that you will not benefit from the microservice architecture. Your legacy process and structure will prevent the microservice architecture from accelerating software delivery. Ultimately, you might even view the migration to microservices as a wasted effort.
A better approach: change everything (incrementally)
In order to fully benefit from the microservice architecture, you must, as described by the success triangle, change your organization’s process and structure.
In particular, you must adopt DevOps as your development process. DevOps, which includes continuous delivery and deployment, is a collection of principles and practices for rapidly, frequently and reliably delivering software.
You must also restructure your organization into loosely coupled, cross-functional teams. Each team includes a product owner and has all the skills needed to turn concepts into code running in production. Each team owns one or more services. The teams collaborate through APIs.
You can change your organization’s development process and structure incrementally. As you migrate your monolithic application to the microservice architecture, you can create loosely coupled, cross-functional DevOps teams to own the services.
To learn more
- Read my Microservices patterns book
- Read or watch my O’Reilly Software Architecture conference keynote
- Talk to me about my microservices consulting and training services including how I can help you create a microservices migration roadmap for your organization
- Learn more about microservices at adopt.microservices.io
microservices adoption anti-patterns
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.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
MICROSERVICES WORKSHOPS
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Learn moreLEARN 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
Remote consulting session
Got a specific microservice architecture-related question? For example:
- Wondering whether your organization should adopt microservices?
- Want to know how to migrate your monolith to microservices?
- Facing a tricky microservice architecture design problem?
Consider signing up for a two hour, highly focussed, consulting session.
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 MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
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.
BUILD microservices
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.
ASSESS your architecture
Consulting services
Engage Chris to conduct an architectural assessment.
Join the microservices google group
Topics
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging
