So far in this series I’ve covered the following anti-patterns
Another anti-pattern that I’ve observed is Focussing on Technology. It occurs when an organization focusses on technology aspects of microservices, most commonly the deployment infrastructure. Unfortunately, focussing on the technology stack is an easy trap to fall into. There are, after all, lots of seriously cool technologies. Kubernetes, Istio and Serverless to name just a few. In addition, there are vendors desperately wanting you to buy their products. If you are a technology VP, spending a lot of money on a vendor’s technology is guaranteed to impress your less technical fellow executives.
One problem with focussing on technology is that it’s undifferentiated heavy lifting. On the one hand, you need put together a technology stack that enables you to deploy services rapidly, frequently, and reliably. But on the other hand, having a good technology stack is not a competitive advantage. It’s far more important to correctly define your services and their APIs.
Another problem with focussing on technology is that it can result in the organization making a big upfront investment in a vendor’s product.
The problem with buying a
$$$ product early on is that the organization chooses the product when it has the least amount of experience with microservices.
There is a risk that the organization chooses a product based on marketing (perhaps targeted at the C-suite) rather than solid technical experience.
Rather than focussing on technology, a better approach is for the organization to focus on the essence of microservices: service decomposition and definition. It should build just enough infrastructure to support what will initially be just a few services. Later, as the number of services grows and the organization becomes more experienced, it can make much more informed decisions about the technology stack.
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.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
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 JUNVCEJE to sign up for $195 (valid until February 1st, 2023). There are deeper discounts for buying multiple seats.
Chris offers numerous resources for learning the microservice architecture.
Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help 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.
Delivered in-person and remotely.
Want to see an example? Check out Chris Richardson's example applications. See code
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
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.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · dark energy and dark matter · deployment · development · devops · docker · implementing commands · implementing queries · inter-service communication · 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 · team topologies · transaction management · transactional messaging