Reactive Programming: Difference between revisions
Jump to navigation
Jump to search
(Created page with " (from Manifesto) Merriam-Webster defines reactive as “readily responsive to a stimulus”, i.e. its components are “active” and always ready to receive events. This d...") |
No edit summary |
||
| Line 14: | Line 14: | ||
* Coursera course "Principles of Reactive Programming." https://www.coursera.org/course/reactive |
* Coursera course "Principles of Reactive Programming." https://www.coursera.org/course/reactive |
||
* The Reactive Manifesto http://www.reactivemanifesto.org/ |
* The Reactive Manifesto http://www.reactivemanifesto.org/ |
||
* Book : Reactive Design Patterns, http://www.manning.com/kuhn/, http://www.manning.com/kuhn/RDP_meap_CH01.pdf |
|||
Latest revision as of 07:58, 4 April 2014
(from Manifesto)
Merriam-Webster defines reactive as “readily responsive to a stimulus”, i.e. its components are “active” and always ready to receive events.
This definition captures the essence of reactive applications, focusing on systems that:
- react to events : the event-driven nature enables the following qualities
- react to load : focus on scalability by avoiding contention on shared resources
- react to failure : build resilient systems with the ability to recover at all levels
- react to users : honor response time guarantees regardless of load
Links
- Coursera course "Principles of Reactive Programming." https://www.coursera.org/course/reactive
- The Reactive Manifesto http://www.reactivemanifesto.org/
- Book : Reactive Design Patterns, http://www.manning.com/kuhn/, http://www.manning.com/kuhn/RDP_meap_CH01.pdf