reactive architecture
Post on 10-May-2015
116 Views
Preview:
TRANSCRIPT
Reactive Architecture
• Based on asynchronous message-passing • Non-blocking using PUSH mechanism• No state, locking, or synchronization
• Share Nothing Architecture• Scale up/out
• => Pay what you consume
• Premiss: Inherently unreliable network & components
• Isolate & encapsulate failure• Redundancy & fault-tolerance as main principles
• Keep latency consistent => real-time• Protect against slow consumers & producers• Use observables models & stateful clients
Bibliography• Reactive Architecture — an overview, http://
www.reactivemanifesto.org• Netflix’ resilience concept,http
://techblog.netflix.com/2011/07/netflix-simian-army.html• Reactive Extensions for the JVM, https://github.com/Netflix/
RxJava• Hystrix — latency & fault tolerance library, https
://github.com/Netflix/Hystrix
top related