Reactive architecture

Reactive programming
“For example, in an imperative programming setting, a := b + c would mean that a is being assigned the result of b + c in the instant the expression is evaluated. Later, the values of b and c can be changed with no effect on the value of a.

In reactive programming, the value of a would be automatically updated based on the new values.

A modern spreadsheet program is an example of reactive programming. Spreadsheet cells can contain literal values, or formulas such as “=B1+C1″ that are evaluated based on other cells. Whenever the value of the other cells change, the value of the formula is automatically updated.”
http://en.wikipedia.org/wiki/Reactive_programming

 

Beginner’s Guide to the Reactive Extensions
http://msdn.microsoft.com/en-us/data/gg577611

 

reactive systems
“In a nutshell, they are systems that are ready to respond to stimuli (whether market data updates, client requests for prices, spreads modifications, position changes, etc), in order to react as quick as possible (in milliseconds or less), in a world where you must constantly protect you against waves or throughput peaks of data coming into your systems.”
http://tpierrain.blogspot.co.uk/2013/07/the-reactive-manifesto_18.html

 

The Technology behind an Equity Trade
http://www.infoq.com/presentations/banking-performance-trading

 

The Reactive Manifesto
Responsive, Resilient, Elastic, Message Driven
http://www.reactivemanifesto.org/

 

 

DevCamp 2010 Keynote – Rx: Curing your asynchronous programming blues
“Asynchronous, event-driven “reactive” programming is way too hard in today’s world of development tools and frameworks. The huge amount of manual and error-prone plumbing leads to incomprehensible and hard to maintain code. As we reach out to services in the cloud, the desire for asynchronous computation is ever increasing, requiring a fresh look on the problems imposed by reactive programming. Centered around the concept of observable data sources, Rx provides a framework that takes care of the hard parts of reactive programming. Instead of focusing on the hard parts, you now can start dreaming about the endless possibilities of composing queries over asynchronous data sources, piggybacking on convenient LINQ syntax.”
http://channel9.msdn.com/Blogs/codefest/DC2010T0100-Keynote-Rx-curing-your-asynchronous-programming-blues

 

Why Rx?
“The world has moved to push; users are waiting for us to catch up. Developers have tools to push data, this is easy. Developers need tools to react to push data.”
Reactive Extensions for .NET (Rx).
“Welcome to Reactive Extensions for .NET (Rx). This book is aimed at any .NET developer curious about the IObservable<T> and IObserver<T> interfaces that have popped up in .NET 4. The Reactive Extensions libraries from Microsoft are the implementations of these interfaces that are quickly picking up traction with Server, Client and Web developers alike. ”
http://www.introtorx.com/content/v1.0.10621.0/01_WhyRx.html#WhyRx

 

Using the WebClient with Reactive Extensions for Effective Asynchronous Downloads
http://www.jaylee.org/post/2010/06/22/WP7Dev-Using-the-WebClient-with-Reactive-Extensions-for-Effective-Asynchronous-Downloads.aspx

 

10. Event-Driven Programming
http://openbookproject.net/thinkcs/python/english3e/events.html

Use cases of EDA Event Driven Architecture
https://cloudramblings.me/2015/04/01/event-driven-architecture-architectural-examples/