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 215 topics
Stream error handling Laurent Caillette 6/25/15
Help on Reactor Net HttpServer Async 马聪 6/18/15
EventBus consume event with several RingBufferWorkProcessor Aviad Hadida 6/16/15
TcpServer/TcpClient example Alexander Baiko 6/15/15
Making my first TcpServer using reactor Laurent T. 6/14/15
Can't make fork-join run (includes test cases) Laurent Caillette 6/12/15
Comparasion to Quasar Samyem Tuladhar 6/11/15
Using EventBus with Processor Aviad Hadida 6/11/15
Training ? Nicholas Whitehead 6/10/15
Want to use a several thread consumer when event is recevied Aviad Hadida 6/7/15
Stream deadlock in simple "diamond-setup" Mathias Doenitz 6/5/15
advice how to use / future reading 6/4/15
2.0.1-RELEASE HttpServer, POST implementation 5/27/15
RxGeode David Dawson 5/23/15
Re: Problem Migrating to the reactor-2.0.1 smaldini 5/21/15
Using reactor to compose a set of related Future with fallback David Dawson 5/19/15
1.x to 2.x migration guide 5/19/15
Switching subscriptions between cold and hot streams David Dawson 5/16/15
Kind words on Reactor and Reactive Streams Laurent Caillette 5/10/15
Feedback on documentation Laurent Caillette 5/10/15
More topics »