Reactive Programming: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
Message-driven runtime. | Message-driven runtime. | ||
=Reactive System Tenets according to the Reactive Manifesto= | |||
* '''Message-driven''' | |||
* '''Resilience''' | |||
* '''Elasticity''' | |||
* '''Responsiveness''' | |||
=Companies= | =Companies= | ||
Revision as of 18:02, 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
- Message-driven
- Resilience
- Elasticity
- Responsiveness
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