Chapter 1. The Journey to Reactive Systems
Enterprises are transforming themselves into cognitive businesses: companies that learn and adapt instantly to the changing conditions around them, using real-time data and AI to bring additional value to their customers. They are realizing this business agility by building applications capable of handling massive scale, massive amounts of data, or both, and running them in a hybrid, multicloud environment.
As enterprise developers and architect leaders within these organizations, you are key influencers. Your recommendations drive the buying decisions that lead to success or failure. The good news is that today you have an unprecedented array of open source technologies on which to base these next-generation applications. That unprecedented array of choices is also the bad news. This report discusses some of the factors driving organizations to employ a reactive-systems approach to cloud native development.
Within this report we define reactive systems as an architectural style that enables applications composed of multiple microservices working together as a single unit to better react to their surroundings and one another, manifesting in greater elasticity when dealing with ever-changing workload demands and resiliency when components fail. We also introduce some of the key patterns found within reactive systems and distinguish between various toolkits and frameworks. Our goal is to help enterprise developers and architects make better ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access