2 ms·

Some additional overview of different reactive approaches: http://www.slideshare.net/deanwampler/reactive-design-languages-and-paradigms http://www.slideshare.

by platz 12y ago

Some additional overview of different reactive approaches: http://www.slideshare.net/deanwampler/reactive-design-languages-and-paradigms http://www.slideshare.net/deanwampler/reactive-design-langua... https://www.youtube.com/watch?v=4L3cYhfSUZs https://www.youtube.com/watch?v=4L3cYhfSUZs * responsive (somewhat hand-wavy - basically, don't block on IO) * scalable (hard to be scalable - many different approaches) * resilient (hard to be resilient - erlang is king here) * event-driven (it's hard to not be event-driven these days)

mattpodwysocki 12y ago
The Reactive Extensions covers all of those particular topics quite well, in terms of responsive to failure, responsive to events, responsive to load etc. We cover that a bit in our repository with the Reactive Manifesto: https://github.com/Reactive-Extensions/RxJS https://github.com/Reactive-Extensions/RxJS And I've even covered it at StrangeLoop 2013: video: http://www.infoq.com/presentations/rx-event-processing http://www.infoq.com/presentations/rx-event-processing slides: https://github.com/Reactive-Extensions/StrangeLoop2013 https://github.com/Reactive-Extensions/StrangeLoop2013 As well as FutureJS: video: https://www.youtube.com/watch?v=zlERo_JMGCw https://www.youtube.com/watch?v=zlERo_JMGCw slides: https://github.com/Reactive-Extensions/FutureJS https://github.com/Reactive-Extensions/FutureJS