Afterword
If you’ve read the whole of this book, you might be thinking something very similar to the feedback an early reviewer gave to me: “Now you have microservices. It will suck. Anyway, you’re depressed now. Bye!”
I’ve focused in this book on the challenges of microservices because that’s the way I tend to approach stuff. Tackling problems is the reason I’m a software engineer, and the aim of this book is to help you be successful with microservices.
While there are challenges, there are lots of positives as well, and I want to focus on those here. Microservices are the right approach in a lot of cases, and they are getting easier to adopt.
In this afterword I want to explain why I think that.
Why Microservices?
People have been building microservices for over a decade now, which means we have a lot of experience about how to do them effectively.
They are a mainstream choice, suggested as a good option by research into what makes for a high-performing technology organization; fitting well with a move to cross-functional autonomous teams; and supported by the rise of a new type of platform engineering, one with a focus on reducing the cognitive load on development teams and enabling them to focus on delivering business value.
The Importance of Flow
We are approaching a decade of State of DevOps reports from the DORA team, and over 36,000 software engineering professionals have contributed to this body of research.
The findings are consistent: for software delivery that has ...
Get Enabling Microservice Success now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
