Reactive programming: lessons learned

День 1 /  / Зал 1  /  EN / Введение в технологию  /  reactive,youarenotnetflix

Комментарий Программного комитета:

Инженерам очень нравятся новые блестящие игрушки. Когда все вокруг тебя говорят о новой технологии, очень трудно удержаться от зуда попробовать ее в своем проекте. Томаш привнесет нотку похмелья и трезвого мышления в это безумство и расскажет, почему не все популярное действительно нужно именно вам.

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?

Tomasz will share some of his 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.



Tomasz Nurkiewicz
Allegro

Java Champion. Spent half of his life on programming, for the last decade professionally in Java land. Loves back-end and data visualization. Passionate about alternative JVM languages. Disappointed with the quality of software written these days (so often by himself!), hates long methods and hidden side effects. Interested in charting, data analysis and reactive programming. Believes that computers were invented so that developers can automate boring and repetitive tasks. Also their own.

On a daily basis works in e-commerce sector. Involved in open source, DZone's Most Valuable Blogger, used to be very active on StackOverflow. Author, trainer, conference speaker, technical reviewer, runner. Claims that code not tested automatically is not a feature but just a rumour. Wrote a book on RxJava for O'Reilly.

Контакты