Reactive Programming: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
* '''Resilience''' refers to form in which reactive systems are delivered. | * '''Resilience''' refers to form in which reactive systems are delivered. | ||
* '''Elasticity''' refers to form in which reactive systems are delivered. | * '''Elasticity''' refers to form in which reactive systems are delivered. | ||
* '''Message-driven''' refers to the means used to implement reactive systems. | * '''Message-driven''' refers to the means used to implement reactive systems. A message-driven system is powered by means of asynchronous, non-blocking communication. This enables first and foremost isolation. | ||
=Companies= | =Companies= | ||
Revision as of 18:06, 20 July 2018
Internal
Overview
The underlying principles of reactive applications inform overall system design.
Message-driven runtime.
Reactive System Tenets according to the Reactive Manifesto
- Responsiveness refers to the value brought by such systems.
- Resilience refers to form in which reactive systems are delivered.
- Elasticity refers to form in which reactive systems are delivered.
- Message-driven refers to the means used to implement reactive systems. A message-driven system is powered by means of asynchronous, non-blocking communication. This enables first and foremost isolation.
Companies
TODO
- The Reactive Manifesto http://www.reactivemanifesto.org
- https://developers.redhat.com/blog/2017/06/30/5-things-to-know-about-reactive-programming
- ReactiveX http://reactivex.io
- https://github.com/ReactiveX/RxJava
- https://blog.takipi.com/reactive-streams-and-the-weird-case-of-back-pressure/
- http://www.reactive-streams.org
- RSocket - steaming message protocol with reactive extension/stream semantics https://github.com/rsocket/rsocket/blob/master/Motivations.md