Oleh Dokuka | Devoxx

Devoxx Ukraine 2018
from Friday 23 November to Saturday 24 November 2018.

Mainly Java Software Engineer / Consultant focused on distributed systems development adopting ReactiveManifesto and ReactiveProgramming techniques. Opensource geek, the active contributor of ProjectReactor. Along with that, Public speaker and Author of the book "Reactive Programming is Spring 5.0":https://www.packtpub.com/application-development/reactive-programming-spring-50

The state of Reactive in the Database's Access


Nowadays Reactive System becomes a trending technique for building Elastic and Resilient Applications. Also, such a technique promotes the reactive, non-blocking and asynchronous communication between components so our system may use resources efficiently. Unfortunately, it means that non-blocking should be supported at all system levels, and one of those layers is a database. In this talk, we are going to expand you a horizon of Reactive interaction with Database. Then, we are going to overview which databases support Reactive access and how it is implemented under-the-hood. Finally, we are going to cover the most important topic which is a Reactive JDBC access, is the state of Reactive here, whether Asynchronous JDBC is reactive and how Pivotal made their own reactive JDBC?

Reactor Netty, Reactor Kafka, what else "Reactor-XXX" is hidden in Spring?


With the 5th generation of Spring Framework, we met a new Reactive WebStack that includes WebFlux, Project Reactor, Reactive Data Access and many other features that allows us to built Reactive System with Spring easily. However, a lot of magic is hidden behind those improvements. Thus, in this section, we are going to mine the most valuable gems and learn how to use it even without Spring Framework.

Our story starts with building a Reactive System using a pure Reactor-Netty. Of course, in order to build full-fledged Reactive System, we are going to use Kafka and enable streaming possibilities with a powerful Kafka client called Reactor-Kafka.

During the talk, we expand our knowledge about those technologies, how they work and how to apply them for building Reactive System.

RSocket - new Reactive cross-network Protocol?


The new generation of cross-service communication is coming and called RSocket. RSocket is a new protocol that embracing Reactive Streams semantic into cross-service messaging. This protocol enables backpressure-control and allows building canonical Reactive-System. Even though the protocol offers asynchronous messages' streaming, there have already been a few competitors in this area by that time. One of those competitors is well-known gRPC. In this session, we are going to learn why RSocket is innovation solution for cross-server communication, can we compare it with gRPC at all and if can, what are the key differences between RSocket and gRPC and why we have to start using RSocket today.

Make sure to download the Android or iOS mobile schedule.