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 92 topics
Reactive Streams in 1.1 or ? Stephane Maldini 4/20/14
ANN Meltdown 1.0.0-beta10 is released Michael Klishin 4/18/14
Execution of Runnables in Dispatcher Luciano Leggieri 4/16/14
THREAD_POOL dispatcher error notify Chen Peng 4/16/14
New Getting Started Guide Jon Brisbin 4/15/14
how to perform parallel tasks at reactor framework with promise or stream 4/11/14
Connected datagram channel (NettyDatagramServer) Ryan Crumley 4/9/14
Graph API to complement Streams Jon Brisbin 4/3/14
Out of Memory Error (AsyncAppender) David Harrigan 4/3/14
Reactor and Chronicle David Harrigan 4/1/14
Is there anyway to get notified if there is no consumer listening for a key? 张斌 4/1/14
Implementing LMAX architecture as described by Martin Fowler Matthew Roper 3/25/14
URI Selector Issue Patrick James 3/25/14
Event handler sequence and thread affinity Venkat 3/20/14
ANN Meltdown 1.0.0-beta8 Michael Klishin 3/16/14
Batch processing applicability Oleg Iavorskyi 3/6/14
Suggestions on deadlock prevention design Oleg Iavorskyi 3/6/14
ANN Meltdown 1.0.0-beta5 is released Michael Klishin 2/25/14
Bunch of Stateful Consumers? Stefan Siprell 2/21/14
Puzzling first attempt... David Harrigan 2/18/14
More topics »