Reactive, or not reactive: that is the question

Day 1 /  / Track 1  /  RU / For practicing engineers

We all know the saying: "If all you have is hammer, everything looks like a nail". In the world of software engineering it usually happens to the new, hyped technologies, which are not always used as they should be. As a result, we get more complex API which can only be supported by the engineers that went through fire and water, lots of bugs, and other problems.

How can we avoid broken fingers and things destroyed by hammer when we try to implement React?

As an example we'll discuss a system with problems and, naturally, try to refactor it in reactive manner. We'll cover benefits and drawbacks of not only the approach, but also API of specific implementations. We'll evaluate the level of complexity before and after refactoring. We'll try to learn what is joke and what isn't.

Download presentation
Kirill Tolkachev

Up until recently Kirill was a lead developer at Alfa-Lab. He was developing different banking APIs, forming principles and tools related to microservice architecture. He is a fan of Groovy, Gradle, Spring and Netflix technologies stack. Kirill is a resident of famous Russian IT-podcast "Razbor Poletov". He knows DevOps methodology like the palm of his hand and has four years' experience of its production usage.

Evgeny Borisov
Naya Technologies

Evgeny is developing on Java since 2001 and took part in a large number of enterprise projects. He went all the way from a simple programmer to an architect, got tired of the routine and became a free artist. Currently, Eugene writes and conducts courses, seminars and workshops for different audiences: live-courses on J2EE for Israeli army officers, Spring — for WebEx for Romanians, Hibernate through GoToMeeting for Canadians, Troubleshooting and Design Patterns for Ukrainians.