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 190 topics
Proactor Pattern Suminda Dharmasena 3/25/15
Project Reactive Evaluation - newbie questions Jocelyn Lepage 3/16/15
Guarantee the order of consuming events? Behrooz Nobakht 3/15/15
Reactor application architecture Jon Poulton 3/11/15
Stream tail calls never executed Jon Poulton 3/11/15
Stream.toList() issue Jon Poulton 3/10/15
Stream.toList() issue Jon Poulton 3/10/15
toList() not executing Jon Poulton 3/10/15
Issue with Stream.toList() Jon Poulton 3/10/15
Issues building HTTP client / server with Reactor Jon Poulton 2/26/15
Best practice to execute multiple async operations and then rendevous back with Reactor? Benson Liu 2/25/15
WatchService with reactor Ajay G 2/24/15
Exception on launching grails app with RC1 version 2/23/15
How to use new Rest API support in 2.0.0.RC1 Alexander Sarkisov 2/19/15
How to implement onSuccess for notify() Martin Kučera 2/11/15
Difference between chain() and broadcastTo()? Joshua Chaitin-Pollak 2/3/15
Understanding Stream.retry() Joshua Chaitin-Pollak 2/2/15
buffer() question Jonathan Gray 2/1/15
Best practices for handling blocking IO requests? Joshua Chaitin-Pollak 1/23/15
race condition in version 2.0.0.M2? Pablo Alcaraz 1/22/15
More topics »