Reactive Functional programming has a lot of promise and even more hype, but introducing a totally new framework can be very invasive and may only be feasible for green field projects.
While most of us love exploring new technologies and methodologies, in reality we are often stuck with adding features and bugfixes on old code, so we're excluded from putting these into practice. This is a fundamental problem: We can't continuously refactor all old code to fit the newest paradigms, but in the long run we also cannot keep writing vintage style code if we want to remain relevant.
Is there a middle road? Rx 'Reactive eXtensions' was initially developed by Microsoft and subsequently ported to many JVM languages by Netflix. RxJava is a regular library and does not require a new framework or methodology to be introduced all across the board. In this talk we'll examine how we can incrementally start using Reactive Extensions, and, equally important, incrementally start reaping benefits.
Reactive Functional programming can improve the overall design of API's, it can improve performance, and it can reduce memory footprint.
I've been CTO of Dexels in Amsterdam for a long time, focusing on architecture for enterprise systems. Recently, I'm also architect at Sendrato, a Wearable computing startup. I'm a bit of a tech fashionista, I'm often looking for the newest tech before it is cool. Balancing that with what's currently useful can be a struggle, but it is always rewarding in the long run. I like to travel and speak at conferences about wildly different topics.
Slides of recent talks are on slideshare: http://www.slideshare.net/FrankLyaruu
Last year Goto London also has a video: https://www.youtube.com/watch?v=qHp1v8lGA9w