Julien Ponge @jponge Principal Software Engineer, PhD

Reactive? (because resources are scarce)

No content

Application

Reactive systems Reactive streams Reactive programming Reactive “Responding to stimuli” Manifesto, Actor, Messages Resilience, Elasticity, Scalability, Asynchronous, non-blocking Data flow Back-pressure Non-blocking Data flow Events, Observable Spreadsheets Akka, Vert.x Akka Streams, RxJava, Reactor, Vert.x Reactor, Reactive Spring, RxJava, Vert.x

while (isRunning) { String line = bufferedReader.readLine(); switch (line.substring(0, 4)) { case "ECHO": bufferedWriter.write(line); break // ... // other cases ( ...) // ... default: bufferedWriter.write("UNKW Unknown command"); } }

x 1000 =

Virtual machines, Containers, etc

No content

(demo)

Vert.x? (async all the things!)

mtpvertx 40% (all Manning)

Eclipse Vert.x Open source project started in 2012 Eclipse / Apache licensing A toolkit for building reactive applications for the JVM ~10k ⋆ on Built on top of https://vertx.io @vertx_project

Http server verticle Database client verticle  Event Bus “Details for user 1234?” “{data}” 4 instances 1 instance

Events Thread Event Loop

Callbacks RxJava 1 + 2 Quasar (vertx-sync) Kotlin coroutines (core) (codegen) CompletionStage

No content

(demo time) APIs with Mongo Edge service with RxJava2 Event streaming with Kafka + web “Connected tires / IoT”

Outro

Unified end-to-end reactive model + ecosystem (not just APIs…) For all kinds of distributed applications (even the small-scale ones) Flexible toolkit, not a framework (your needs, your call)

Asynchronous programming

Single threaded event processors vs multi-threaded components

Do you really need these anaemic POJOs / DTOs?

Not everything has to be annotations!

Powered by and more!

mtpvertx 40% (all Manning)