Reactive development has become a trending topic in many developer conferences, meetups, blog posts, and countless other content sources (both online and offline).
But what is a reactive application? The Reactive Manifesto provides an official definition; you can find it at https://www.reactivemanifesto.org for more details.
In short, according to the manifesto, reactive systems are as follows:
- Responsive: The system responds promptly if possible.
- Resilient: The system stays responsive in the face of failure.
- Elastic: The system stays responsive under varying workloads.
- Message-driven: Reactive systems rely on asynchronous message-passing to establish a boundary between components, which ensures loose coupling, isolation, and location transparency.
This chapter shows you how to use the Jakarta EE 8 features to meet...
