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 227 topics
Robust hot stream examples. 9/2/15
Error handling in Streams Gesly George 8/19/15
projectreactor with Netflix Hystrix Amardeep Singh 8/3/15
HashWheelTimer - allocating more threads Gesly George 7/21/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
Delimited Codec Behavior James Bridges 7/9/15
Reactive Polling Fedor Vostrikov 7/9/15
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
More topics »