Let’s talk Reactive. No, not React. Reactive. As in, let’s-handle-streams-of-data-coming-in-very-fast-like-this. Or are we talking about system design principles? Or are we talking about…you know what, we’ll let this month’s speaker, the excellent Fabio Tiriticco, explain. He’ll be walking you through all the different shades of Reactive and explaining what they can do for you.
With food, drinks and space graciously delivered by the fine folks of DHL, it’s going to be a great time!
19:00 – Doors open
19:30 – Welcome
19:35 – Talk: Reactive Programming or Reactive Systems? (Spoiler: both)
20:25 – Raffle & News
20:30 – Social!
Talk: Reactive Programming or Reactive Systems? (Spoiler: both)
The word ‘Reactive’ seems to be all over the place these days – and together with it, a great deal of confusion. We’ll look at the difference between Reactive Programming and Reactive Systems, both with concepts & code examples in Scala.
Speaker: Fabio Tiriticco (@ticofab)
One day, a few years ago, Fabio Tiriticco was looking at existing technologies to realise his startup idea. An initial test with classic multi-threaded Java programming lead to successful-yet-ugly&painful results. That is when Scala & Akka came into sight. The startup didn’t go very far, but the love for Reactive Systems stayed strong ever since. By day, Fabio works as a Tech Lead for Weeronline.nl, while at night he runs the Reactive Amsterdam meetup.