Spring Reactive Ripper

Day 2 /  / Track 1  /  RU

You all heard the phrase: "A person who learned how to use a hammer begins to see a nail in everything". In the programming world, it often happens with new and trendy technologies and is not always used for intended purpose. As a result, we have a more complex API that only experienced programmers can support, a lot of bugs and other problems.

How we'll try to avoid broken fingers and hammered things while trying to implement React?

We will consider the system example that has problems and of course, we will try to refactor it in a reactive style. Also, we will consider the advantages and weaknesses of approach and API specific realizations. We will evaluate the complexity that was before refactoring and the complexity that we inserted after. And try to figure out what are toys and what is not.

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.

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.