Reactor, as the name suggests, is heavily influenced by the well-known Reactor design pattern. But it is also influenced by other event-driven design practices, as well as several awesome JVM-based solutions that have been developed over the years. Reactor's goal is to condense these ideas and patterns into a simple and reusable foundation for making event-driven programming much easier.

Reactor’s abstractions give the developer a set of tools to not just develop but compose applications in a way that more efficiently uses system resources--which is particularly important when running in the cloud--and reduce or eliminate the spaghetti of nested callbacks (aptly named “callback hell”) that has so far burdened most asynchronous applications.

Showing 1-20 of 236 topics
stack overflow when doing error handling. Ymo Lists 2/1/16
Error handling in Streams Gesly George 1/26/16
Reactor event bus supports spsc and mpsc queues ? Ymo Lists 1/21/16
Detecting switch from hot to cold David Dawson 12/3/15
Where is reactor.Environment and reactor.core.Dispatcher Alain Picard 11/23/15
Centralized EventBus Andrea T. 11/22/15
HashWheelTimer - allocating more threads Gesly George 10/14/15
Reuse of actions in different stream instances Daniel Feist 10/5/15
Custom reactive data-sources Jesper Blomquist 10/2/15
Reactor on Grails 2.4.4 9/28/15
Data lost in cold stream Markus Paaso 9/28/15
Robust hot stream examples. 9/2/15
projectreactor with Netflix Hystrix Amardeep Singh 8/3/15
Best practices for handling blocking IO requests? Joshua Chaitin-Pollak 7/18/15
Theory behind Reactor Jernej Jerin 7/17/15
Reactor with Chronicle, performance Vijay Veeraraghavan 7/16/15
Measuring number of in-flight data in unbounded Stream consuming Jernej Jerin 7/16/15
EventBus vs Stream, when to choose streams over the eventbus Vijay Veeraraghavan 7/14/15
Stream.broadcast() behavior Gesly George 7/10/15
Clarification - Broadcaster vs Processor? Gesly George 7/9/15
More topics »