One key benefit of reactive systems and reactive REST endpoints is efficiency. This workshop describes how to use reactive systems and reactive programming to achieve faster response times. Especially in public clouds where costs depend on CPU, RAM and compute durations this model saves money.
The workshop uses a sample application to demonstrate reactive functionality. The sample application displays links to articles and author information.
The sample contains a 'Web-API' service with two versions of the endpoint '/articles', one uses imperative code, the other one reactive code. In this workshop you'll re-implement a simplified version of the reactive version yourselves.
The reactive stack of this sample provides response times that take less than half of the time compared to the imperative stack:
If you want to know more details, you can read the documentation of the performance tests.
The following architecture diagrams do explain the complete flow the sample application.
The 'API Client' invokes the 'Web-API' service which implements a backend-for-frontend pattern.
The 'Web-API' service invokes the two microservices 'Authors' and 'Articles'. The 'Articles' service reads data from Postgres.
Note that in this workshop you will deploy the full application as described in the previous diagram. But to simplify the workshop you'll re-implement a simpler version of the 'Web-API' service which only invokes the 'Articles' service.
Estimated time and level
After you complete this workshop, you'll understand the following reactive functionality:
Reactive REST endpoints via CompletionStage
Exception handling in chained reactive invocations
Timeouts via CompletableFuture
Reactive REST invocations via MicroProfile REST Client
The intention of this workshop is not to explain every aspect of reactive programming, but to explain core reactive principles and to deploy a complete reactive application which you can inspect after the workshop in more detail.
About this workshop
The introductory page of the workshop is broken down into the following sections: