Software's Soul - BSC

Meet-up at DevDay Lately i've conducted a meet-up at DevDay , an Italian Developer Community,  to present the Reactive Programming Paradigm and Reactive Extension. I believe in this approach and would like to share my experience, so I've presented a "slide deck" (embed at the end) and below is reported its summary. 1. The Reactive Manifesto I've briefly introduced the Reactive Manifesto , underlining which are, in my opinion,  the most important concepts coming out from it: Asynchronous non blocking Message Driven  back-pressure Resilient 2. Why use Reactive Why the Reactive Systems are becoming so important in the modern age of the Microservices & Cloud ? In this part I have introduced the importance of  : Let's do it asynchronous  Async != Multi threads Async == Never Block Immutable State 3. When to be Reactive  When Reactive Programming could help you ? For developing which Applications ? In particular...

Reactive World Is almost one year that I have started to learn the reactive world , I began from its manifesto and i continued applying it in development of my Open Source projects and  in particular through the  languages JavaScript (and then RxJS ), Java (and then RxJava ) and Swift (and then RxSwift ) Why Reactive ? I nitially I approached reactive paradigm like a kid that open the gift box with a new and unknown toy, mostly fascinated by the technological wave that carried with it a lot of “ new ” stuff like: functional programming , stream/event oriented programming , backpressure , “ callback hell ” solver . But as always “ all that glitters ain't gold! ” and our capacity to understand context of problems make the real difference and help us to choose the right approach, language, paradigm and frameworks to put on the table. Better explain by examples So I would share with you some problems in particular contexts that I have dealt with rea...