If you want your application to provide millisecond response times and close to 100% uptime, traditional architectures with single SQL databases and thread-per-request models simply cannot compete with microservices. This report discusses strategies and techniques for building scalable and resilient microservices, and helps you work your way through the evolution of a scalable microservices-based system. When it comes to development speed, time-to-market, and continuous delivery, microservices can do wonders for your organization. Author Jonas Bonér, Founder and CTO of Lightbend and author of Reactive Microservices Architecture (O’Reilly), demonstrates how to refactor a monolithic application step-by-step. You’ll briefly land at single instance microliths (micro monoliths) before working your way toward a scalable and resilient microsystem. This report will help you: - Examine the essential traits of an individual reactive microservice - Understand why monolithic architectures are a problem - Manage the hard part of microservice design: the space between individual services - Shift the focus from domain objects to events in domain-driven design - Make services more efficient, performant, and stable by applying reactive programming techniques - Make the services work together, collaboratively, as a single reactive system - Move beyond CRUD towards Event Sourcing/CQRS to scale state in an event-based design - Leverage fast data in microservices to manage real-time data at scale
It is excellent book about microsystems (microservices). Book starts with a monolithic application and then convert it to a microsystems. It also looks at techniques from reactive systems, event-driven programming, domain-driven design, event sourcing, etc. The book also examines the challenges in this area and provides appropriate solutions I recommend this book to anyone interested in microservices.
As with most of the other Boner's Reactive books I've happened to read, this one is also a Lightbend infomercial that offers a fairly simplified overview of the subject matter but compensates for that by offering decent references. To quote Anatoly - not great, not terrible.
It's a great overview. It does leave one wanting to dig deeper on so many things with not much guidance on how to turn theory into practice. The author would probably say "just use Akka" but not everyone is going to be willing to do that.
Probably the best overview about reactive microservices I've read. History starts with a monolith. The author describes its drawbacks and gives some ideas on how to solve them. It gives a beef description of different strategies of decoupling systems like event-driven design, reactive messaging, or even event-sourcing; what's really a big plus, it the fact that the author (usually) doesn't hide the drawbacks and pain points of these solutions but explains them pretty well. Also, it contains a good but short definition of what Domain Driven Desing is and why it's really way going in a distributed world. Probably only one of the important con of this book is a bit too hyped description of Event-Sourcing.
A very well written continuations of "Reactive Microservices Architecture" covering not in very depth all the areas about Distributed systems and Reactive Systems. Even if the book is not in depth, Jonas Boner let a lot of links and references to very valuable papers, books and blog posts written by distributed systems experts in various fields.