Continuing on our reactive journey, we will now talk about major building blocks of reactive programming (functional reactive programming to be precise) and what concerns a reactive microservice should actually handle. The following is a list of major building blocks of reactive programming and what they all handle. A reactive microservice should be designed on similar principles. These building blocks will allow us to make sure that a microservice is isolated, has a single responsibility, can pass a message asynchronously, and is mobile.
An oservable streams is nothing but an array that is built over time. Instead of being stored in memory, items arrive asynchronously over time. Observables can be subscribed to, and events emitted by them can be listened to and reacted upon. Every reactive microservice should be able to deal with native observable streams of events. An observable allows you to emit values to the subscriber by calling the...