The Reactive Manifesto was first introduced by Jonas Bonér (@jboner) in his blog post (https://www.lightbend.com/blog/why_do_we_need_a_reactive_manifesto%3F) in 2013. It has been updated in its second version and the full text can be accessed on http://www.reactivemanifesto.org/.
Reactive Systems have the following traits:
- They react to their users (responsive)
- They react to failures and fully recover (resilient)
- They react to variable loads (elastic)
- They react to inputs (message-driven)
As the manifesto puts it, systems built as Reactive Systems are more flexible, loosely-coupled, and scalable. This makes them easier to develop and amenable to change. They are significantly more tolerant of failure, and when failure does occur, they meet it with elegance rather than disaster. Reactive Systems are highly responsive, giving users effective interactive...