Iterating to Reactive


Scaling existing applications to provide extreme throughput can be very difficult. Single-threaded processing becomes a performance bottleneck while traditional parallelization can be difficult to write and maintain. The Reactive Streams API attempts to solve these issues by providing the developer an easy-to-use API to tackle the complexities of concurrency and resource management.

However, not everyone has the luxury of starting a new application with a reactive-first design. In this session, Matt Klooster, VP Software Engineering at JPMorgan Chase Chase and Mark Sinclair, VP Software Engineering at JPMorgan Chase. will go over strategies to iteratively migrate existing applications to take advantage of the Reactor API. Large-scale redesign projects are often not viable for existing production applications. To avoid these situations we can work portions of code into smaller streams before eventually joining them to complete the end-to-end reactive flow.