Introduction to the series
More than ever before, organizations ask us questions like What does Reactive really mean and why should we care? What does “Going Reactive” mean for our Development and Operations teams? What are the business drivers and market forces that we should be aware of, and how can my organization start the journey towards modernizing our existing applications and infrastructure?
From Jonas Bonér, Viktor Klang and Konrad Malawski, co-author of the Reactive Manifesto and contributors to the Reactive Streams initiative, we have set out to produce a three-part “Reactive Revealed” series to give an interactive opportunity for developers, architects and executives alike to get started with understanding Reactive from the beginning, providing an overview of the technological foundation behind it all.
Reactive Revealed 1/3: Async NIO, Back-pressure and Message-driven vs Event-driven
In this first of three webinars with live Q/A, we explore the underlying technologies and approach of Reactive systems. Akka Team member and Reactive Streams contributor Konrad Malawski will detail what you should know about:
The differences and trade-offs between synchronous blocking I/O and asynchronous non-blocking I/O, what these mean for execution efficiency as well as code maintainability.
The difference between event-driven and message-driven approaches in terms of design considerations in the small and the large as well as the costs and benefits of either way.
The role of flow control in Reactive systems, how it impacts service latency and throughput and which technologies are available to help with implementing it.
In the next webinar with Viktor Klang, we review the role of elasticity, scalability and location transparency. In the third and final webinar in the series, with Jonas Bonér, we continue with learning about resiliency, errors vs failures, isolation (and containment), delegation, and replication in Reactive systems.