discusses reactive systems and honey bees with
summary
Explains that reactive programming is a practical tool for microservices and that reactive systems follow the Reactor Manifesto to be responsive resilient elastic and message-driven. Describes actor-style services, nonblocking reactive streams and event-driven messaging as the actual tools used, compares decentralized fault tolerance to honeybee role behavior, and claims this design scales to hundreds of simultaneous users while preserving responsiveness under failure.
AI-written summary · about
chapters (3)
related talks
13mReacting to the future of application architecture
42mReacting to the Future of Application Architecture
55mRethinking Reactive Architectures
46mGet Reactive! Programming, Systems, and Microservices
42mReactive Design Patterns
40mReactive programming: lessons learned
59mSucceeding at Reactive Architecture
39mReactive Programming