Reactive hardcore. How to implement Publisher> and beyond (15:20 - 17:15 on Tuesday)
The more popular Reactive Programming/Libraries becomes, the more often we have to deal with those techniques and solutions. Sometimes we have to deal just with smoothies API of Reactive Extensions, sometimes we have to dive into the internals of those libraries, or sometimes we have to build own implementation. Nevertheless, understanding of the basics patterns, behaviors that are hidden inside the most of Reactive Libraries, Tool-Kits / Best Practice might simplify our – life with / debugging of / implementation of Reactive Library. Usually reading a tone of papers and blogs about the internals of Reactive Libraries, specific rules of Reactive Streams Specification or simply grasping the source code becomes hardcore. Hence, we will summarize all important by implementing own Publisher<> using Java. What will we do to learn? We will: * Remind the sense and importance of Reactive Streams Specification. * Naively implement our first solution and fail of course. * Find toolkit which will help in verification of the implementation. * Iteratively follow all the rules of Reactive Streams and implement the correct solution. * Step by step create our own Reactive Library * Compare our solution to what we have, for example, in Project Reactor and ensure that used patterns are same. * Summarize best practices and recap patterns used in the demo.
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