Chapter 2. Defining Reactive Systems
Reactive systems are already in use in a wide variety of industries and use cases. But, what makes them reactive systems? How is this defined, and what makes a reactive system truly reactive? What tools or implementations are needed to achieve this complete reactivity?
The Need for a Manifesto
Prior to 2013, reactive systems were virtually unknown. However, today “reactive” has risen in popularity and is being adopted by more and more Fortune 2000 companies. This is a direct response to enterprises’ need to design and build applications capable of handling massively increased scale and quantities of data. However, this widespread adoption has led to the creation of a huge variety of implementations and various versions of “reactive.” So, how do we define exactly what a standard reactive system is across the industry?
In 2013, the Reactive Manifesto was created to do exactly this. This manifesto was conceived with the aim of condensing all of the knowledge we had accumulated as an industry in designing and building highly reliable and scalable applications. It then distilled this knowledge into a set of required architectural characteristics that would make any application flexible, loosely coupled, and elastic. It also carved out a defined vocabulary to enable efficient and clear communication between all participants, including developers, project leaders, architects, and CTOs.
The Reactive Manifesto lays out four key high-level characteristics ...
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