Need of Reactive Manifesto

We need to understand what the main need of Reactive Manifesto is, so that we will get clear picture about it.

The main needs or goals of Reactive Manifesto are as follows:

• Users or customers need responses in a timely manner. They don't like slow responses and they don't use slow systems. If they don't get quick responses as needed, they will look for other options.
• We should have an API to support asynchronous streaming data with non-blocking backpressure.
• API for Reactive Technology (frameworks, tools, languages, IDEs, and so on) implementors.
• Heterogeneous Reactive systems should work in an interoperable way.
• We should have a better approach for consumers to avoid buffer overflow issues.