With nearly 4000 people registering for the complete Reactive Revealed series, we're happy to conclude this exposed look into the bits and pieces that have defined the Reactive Manifesto, the Reactive Streams Initiative, and also the driving force behind our Reactive Platform and ConductR.
In Part 1, Akka engineer Konrad Malawski discusses the role of asynchronous, non-blocking I/O, back-pressure and the message-driven vs. event-driven approach in Reactive systems. In Part 2, Typesafe deputy-CTO Viktor Klang discusses how elasticity, scalability, location transparency and other traits are at the heart of Reactive systems.
In this final part, Jonas Bonér, Typesafe CTO/co-founder and creator of Akka, explores the nature of Reactive systems and how they maintain resiliency with an infrastructural approach designed to welcome failure often and recover gracefully. Specifically we review:
Have you ever wondered how companies like LinkedIn, Netflix, SalesForce, Twitter and Walmart design (or in many cases, redesigned) their modern architectures? This wasn't by accident. Check out over 50 success stories from our customers and enterprises in the community, or get in touch with someone at Typesafe regarding our consulting services, such as code and architecture reviews as well production readiness reviews. Don't wait for it to fail, let's chat today!
