Reactive Programming has the edge

Reactive Programming is now taking the world by Storm. Previously we would building the application in a sequential manner. We would wait for the update from each of the service calls and proceed to next statement on execution.

Reactive Programming gives the edge by not waiting for the output from the service and moves to the next line of execution.

The lazy evaluation of the functional programming can be very well used by the Reactive programming.Initially it provides the handle for processing from the server side.

The data is passed between the client and server is in the form of data-stream.This uses the streaming capability for passing on the data and retrieving the update at a later point of time. One of the

Initially it was done before as

public String downloadContents(URL url) throws IOException { try(InputStream input = url.openStream()) { return IOUtils.toString(input, StandardCharsets.UTF_8); } } //... final String contents = downloadContents(new URL("http://www.example.com")); In the Reactive Programming

public static Future<String> startDownloading(URL url) { //... } final Future<String> contentsFuture = startDownloading(new URL("http://www.example.com")); //other computation final String contents = contentsFuture.get();

We will implement startDownloading() later. For now it's important that you understand the principles.startDownloading() does not block, waiting for external website. Instead it returns immediately, returning a lightweight Future<String> object. This acts like a proxy of wrapper for getting the data. Once the asynchronous process is over it returns the data.