Chapter 6. Playing with Server-Sent Events
In Chapter 4, Kotlin Basics and Spring Data Redis and Chapter 5, Reactive Web Clients, we created two microservices. The first one is responsible for keeping tracked data on Redis and triggering the second microservice which one will consume the Twitter stream. This process happens asynchronously.
In this chapter, we will create another microservice which will consume the data produced by Twitter Gathering and expose it via a REST API. It will be possible to filter Tweets by text content.
We have consumed the Twitter stream using the Server-Sent Events (SSE); we created a reactive REST client to consume that. Now, it is time to create our implementation for SSE. We will consume the RabbitMQ queue and push the data to our connected clients.
We will take a look at the SSE and understand why this solution fits well for our couple of microservices.
At the end of the chapter, we will be confident about using SSE in the Spring ecosystem.
In this chapter, we...
