View on GitHub


Workshop: Reactive Messaging with Quarkus on OpenShift

Workshop: Reactive Messaging with Quarkus on OpenShift

This workshop is also documented in an easier readable and navigable version using GitBook. You can access this version with this link.

In this workshop you’ll learn how to implement reactive messaging functionality with Java, Quarkus, Kafka, Vert.x and MicroProfile. An end-to-end sample application will be deployed to Red Hat OpenShift.

The code is available as open source as part of the Cloud Native Starter project.

One benefit of reactive models is the ability to update web applications by sending messages, rather than pulling for updates. This is more efficient and improves the user experience.

The workshop uses a sample application to demonstrate reactive functionality. The simple application displays links to articles and author information.

Articles can be created via REST API. The web application receives a notification and adds the new article to the page. The animation shows how curl requests are executed at the bottom which trigger updates to the web application at the top.

The next diagram explains the flow between the different components and microservices.

The API client ‘Submissions’ triggers the REST API of the ‘Articles’ service to create new articles. The ‘Articles’ service sends a message to the ‘Web-API’ service via ‘Kafka’. The ‘Web-API’ provides a streaming endpoint that the web application ‘Web-App’ consumes.


After you complete this workshop, you’ll understand the following reactive functionality:

This workshop is for beginners and takes one hour.

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.

Get Started

These are the labs of this workshop, go through all of them in sequence, start with lab 1:

What to do next

The blogs as well as the presentation describe the functionality in more detail.

There is a second workshop which uses the same sample application. That workshop is called Reactive Endpoints with Quarkus on OpenShift and it focusses on reactive APIs and API invocations.