Anti-microservice architecture tweets still generate lots of engagement:
Microservices are such a fundamentally and catastrophically bad idea that there are going to an entire cohort of multi-billion companies built that do nothing but contain the damage that they have wrought.— Nick Schrock (@schrockn) October 16, 2020
On the one hand, there’s an element of truth to this tweet. For example, some organizations have mistakenly treated microservices as a magic pixie dust and used them inappropriately. What’s more, a key principle when considering adopting microservices is to first make the most of your monolith.
But on the other hand, this argument is about as useful as a stopped clock. The idea that you should never use microservices is quite absurb:
Yes. I've heard rumours that Netflix, Uber and Amazon have all recognized that microservices are a giant mistake. They are all busy merging all of their respective services into a giant application.exe that will be released on April 1, 2021.😜— Chris Richardson (@crichardson) October 17, 2020
(Note: I so hope these companies are not considering this 🤞🏾😀)
The reality is that which architecture you should pick for your application depends on your requirements. If you are a small team of developers then you should probably start with a monolith. But as your application and its team grows from very small to very large, it’s likely that at some point you will outgrow your monolith. Development and delivery - as measured by deployment frequency and lead time - will, for example, slow down. At that point sticking with your monolith could very well be a mistake and you should consider migrating to a microservice architecture.
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