What did I know last week about reactive programming? Nothing. That´s a fact. However, I started reading about and I find the topic really really interesting.
Unfortunately, there is not much documentation around (or at least, I had a hard time finding it) so I would like to share some resources with you along with an example that I have adapted to perform like our module Stokker (the module that used to fetch stock quotations from Yahoo Finance for us using Spring Integration).
What is Reactive Programming?
The best definition I could find was this amazing GitHub gist written by @andrestaltz that summarizes all the theoretical definitions to this line:
Reactive programming is programming with asynchronous data streams.
I really recommend to you its reading, but we can summarize it in:
- You will work with immutable event streams to which you will have to subscribe.
- Some operations will be provided to you, so you can transform these streams into new ones by filtering them, merging them o create new events from the previous ones.
|Two event streams: One with numbers, the other with each element multiplied by 10|
The first line, represents an initial event stream. In the middle you can see the mapping function that is applied to every event in the stream and finally, the second stream with the results:
Note: Pay attention to the immutability here: Any transformation you apply to a stream creates a new one!
Let´s check out another transformation:
|Two event streams: One with numbers, other with the average of the elements received|
Look who is here! Our old friend, the moving average. Whenever a new event arrives in the original stream, a new value for the average will be calculated in the resulting stream.