Reactive Architecture/Programming Responsive respond in a timely manner if at all possible. detected...

Please Visit: http://ift.tt/1ajReyV

Reactive Architecture/Programming

Responsive
respond in a timely manner if at all possible. detected problem quickly and dealt with effectively

Resilience is achieved by replication, containment, isolation and delegation

Elastic: The system stays responsive under varying workload. 
This implies designs that have no contention points or central bottlenecks, resulting in the ability to shard or replicate components and distribute inputs among them.
performance monitoring

Message Driven: Reactive Systems rely on asynchronous message-passing to establish a boundary between components that ensures loose coupling, isolation, location transparency, and provides the means to delegate errors as message

http://ift.tt/17j97hu
http://ift.tt/1A91LzO
http://ift.tt/1J48RYa

RxJava
Async By Default, Callback
onSuccess.onFailure
https://www.youtube.com/watch?v=_t06LRX0DV0
Observable + Time
Timeout in distributed system
Retry

The Reactive Manifesto. Published on September 16 2014. (v2.0). Organisations working in disparate domains are independently discovering patterns for building software that look the same. These systems are more robust, more resilient, more flexible and better positioned to meet modern demands.

from Public RSS-Feed of Jeffery yuan. Created with the PIXELMECHANICS 'GPlusRSS-Webtool' at http://gplusrss.com http://ift.tt/1F9GGl0
via LifeLong Community