Reactive programming promises higher performance of Enterprise Java applications with lower memory requirements. This promise is achieved by avoiding blocking calls that always lead to process and context switches in the operating system. Such context switches have a high CPU and memory overhead, which, of course, is reduced by fewer of such switches. However, this performance gain of reactive programming comes at the price of poorer maintainability of the software. But is the higher performance worth the price and what are the alternatives? Let’s take a closer look at this in this article.
Reactive Programming and observables are really powerful and go beyond what promises offer. They provide key features like laziness and the ability to cancel them. This allows you to add robustness into Angular 2 applications especially at the level of HTTP to finely control what is executed.
Tim Fox of Red Hat explains the basics of Vert.x and how it will help bring us into a reactive future.
Typesafe’s Jonas Bonér explains why the Reactive Manifesto is key for the for the future of high quality development – and why its good news for Java devs.
Jamie Allen holds forth on Java 8 Lambda hype, Scala love, and breaking down reactive programming. Filmed backstage at JAX London 2013.