From Monolith To Microservices
Cloud native applications require agile architectures based on microservices that typically use containers like Docker and orchestration platforms such as Kubernetes. Importantly, one microservice is no microservice—they come in systems. It's in between services that the most interesting and challenging things take place.
In these concise O'Reilly reports, Jonas Bonér, co-author of the Reactive Manifesto and creator of the Akka project, provides architects and technology leaders with an overview of the principles and strategies they should consider when designing systems of microservices for cloud native applications.
In Reactive Microservices Architecture: Design Principles For Distributed Systems, Bonér explores microservices from first principles in its true context: distributed systems.
- Examine the essential traits of an individual reactive microservice
- Shift the focus from domain objects to events in domain-driven design
- Manage the hard part of microservice design: the space between individual services
Building on these principles, Bonér provides a step-by-step approach to refactor your traditional monoliths into cloud native systems of microservices in, Reactive Microsystems: The Evolution of Microservices at Scale
- Understand refactoring tradeoffs for modernizing existing monoliths
- Examine why microservices need to own their state, exclusively
- Make services work together, collaboratively, as a system