Microservice Architecture
Supported by KongMicroservices adoption anti-pattern: Trying to fly before you can walk
So far in this series I’ve covered the following anti-patterns
Another anti-pattern that I’ve observed is Trying to fly before you can walk. It occurs when an organization attempts 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.
Quite often, management continues to be focussed on schedule and features and consequently overlooks key software quality attributes, such as maintainability, testability and code coverage.
Consequences
Trying to adopt microservices without practicing the basics of software development is likely to lead to disappointment. The microservice architecture requires good design skills and test automation. A badly designed microservice architecture that lacks automated tests is likely to be worse than a monolith. Moreover, messy code will reduce your ability to deliver software rapidly and frequently.
A better approach
When adopting microservices, an organization needs to embrace fundamentals, such as:
- Clean code - implement automated code quality enforcement as part of the deployment pipeline
- Automated testing - developers must be required to write automated tests as part of development. While test coverage is not the best metric, it should also be enforced by the deployment pipeline. Also, while test-driven development (TDD) is not mandatory, an organization might want to require it initially in order to instill the testing habit.
- Design skills - such as object-oriented design (OOD) or Domain-driven design (DDD). Services must have stable, well-designed APIs. Also, in order to avoid creating a distributed monolith, which requires numerous services to be changed in lock step, developers need to have the design skills to carefully define service boundaries and responsibilities.
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
