All videos
All videos
Reactive programming: lessons learned
April 16, 2018
Reactive programming enables amazing things. Highly scalable systems consuming just a fraction of CPU compared to ordinary applications? Sure. Responsive, low latency and high throughput? No problem. Small memory and OS footprint? Out-of-the-box. Any reason not to love reactive? I will share some of my experiences with reactive programming and systems. Where it shines and where it was an over-engineering. What are the hidden costs and common mistakes? How to convince your teammates to start the reactive journey. And more importantly: how to convince your teammates, that going reactive is a dead end. On a case-by-case basis.
Tags
Other videos that you might like
![fallback image](https://img.youtube.com/vi/Hxoj1tcuAbo/hqdefault.jpg)
Beyond the hype: reactive vs traditional microservices
Marcin Zagórski, Paweł Dolega, Łukasz Biały
![fallback image](https://img.youtube.com/vi/vrHIIuzXIps/hqdefault.jpg)
Applying principles of chaos engineering to Serverless
Yan Cui
![fallback image](https://img.youtube.com/vi/Nft-rcB9Bu4/hqdefault.jpg)
Panel discussion on Reactive Systems
Samuel Weiss, Trevor Burton-McCreadie, Łukasz Biały, Alan Klikić, Paweł Dolega
![fallback image](https://img.youtube.com/vi/fY95d4rCBUs/hqdefault.jpg)
Fast Data Architecture at XITE
Roman Ivanov