Quarkus is not only a Kubernetes-native stack offering an incredible developer experience, it's also a reactive framework. You notice this reactive nature when building event-driven microservices, but will see it also provides nice perks for HTTP and REST applications. In this talk, we will explain how the reactive engine of Quarkus allows implementing synchronous HTTP APIs as well as asynchronous ones, and how you can use the power of the reactive core of Quarkus to build extremely concurrent applications. Along with the talk, many demos exhibit various reactive features, such as reactive routes, streaming JSON, server-sent-events, and how you can interact with the various reactive APIS such as Hibernate-Reactive and gRPC.

1. Take the highway:
Reactive routes

2. Take the highway:
Reactive routes MUTINY!

3. AHOY! Reactive
A Pirate’s journey

4. 4

5. @
@</>
@
@
</>
Build Time
Runtime
RuntimeBuild Time

6. 6
Developer Joy Supersonic Subatomic Java
Unifies
Reactive and Imperative
Best of breed
libraries and standards

7. Why Reactive?
REACTIVE

9. BETTER
RESPONSIVE
ASYNC MESSAGE
PASSING
ELASTICITY RESILIENCE

12. Batten Down The Hatches!

13. concurrency
Run on the I/O Thread
}I/O Thread
Application Code
Reactive Framework
Non-Blocking I/O

14. Son of a biscuit eater!

15. Reactive Endpoint
Extensions
Non-Blocking I/O (Vert.x)
Routing layer
No need to switch
No need to switch

16. Imperative
Extensions
Non-Blocking I/O (Vert.x)
Routing layer
Dispatching on a
worker thread
Switch back to I/O
thread

17. Shiver me timbers!

18. The Quarkus Reactive
Quest

19. Reactive Quark

20. Reactive Quark
The CRUD Trench

21. Application Code
Extensions
Blocking I/O

22. Run on the Worker
Thread Thread
}Worker Thread
Application Code
Extensions
Blocking I/O

23. Reactive Quark
The Vert.x
Cape

24. Application Code
Extensions
Blocking I/O
Vert.x
Non-Blocking I/O
Can use a reactive path
Managed Vert.x instance

25. Reactive Quark
The HTTP
Island

26. Application Code
Extensions
How can we handle both
Reactive and Imperative?
Non-Blocking I/O (Vert.x)
Vert.x HTTP Server
Vert.x Web Router

27. JAX-RS
Extensions
Non-Blocking I/O (Vert.x)
Routing layer
Dispatching on a
worker thread
Switch back to I/O
thread

28. Reactive Endpoint
Extensions
Non-Blocking I/O (Vert.x)
Routing layer
No need to switch
No need to switch

29. Reactive Quark
The Kafka Monster

30. Application Code
Extensions (Reactive + Imp.)
Non-Blocking I/O (Vert.x)
Routing layer

31. Application code
Extensions
Non-Blocking I/O (Vert.x)
Routing layer
MUTINY!
All reactive APIS are
exposed using Mutiny!

32. Reactive Quark
Mutiny
volcano

33. Reactive Quark
Reactive Bay

34. Reactive Quark

35. Reactive Endpoint
Extensions (Reactive + Imp.)
Non-Blocking I/O (Vert.x)
Routing layer
Vert.x ecosystem
Hibernate Reactive
Camel Reactive

36. REACTIVE + IMPERATIVE
REACTIVE
QUARKUS =

37. https://github.com/cescoffier/ahoy-reactive