RESTEasy Reactive : why should I care?
Stéphane Épardaud, Red Hat. @UnFroMage
We always need a plan, even if we don’t follow it
● A brief glimpse at why you should care about async, reactive, blocking
○ And all those event-loop, IO Thread, Worker Thread terms that hipsters and C programmers
use
● How can I turn my REST endpoints from rusted, slow, old-style to golden
buzzword-enabled syrup?
○ DEMO!!!
● This item was placed here just to check if anybody is reading this, but it
doesn’t matter we won’t have time to cover it anyway
● Recap and Questions
Alright, why should I care?
Traditional architecture: IO and worker threads
But… they’re all sleeping???
User
More efficient architecture: non-blocking by default
A truly modern architecture
So what is RESTEasy Reactive?
● JAX-RS implementation redone from scratch (client and server)
● Built for Quarkus
○ Async by default, using Vert.x
○ Reactive support with Mutiny
○ Ultra-fast architecture
■ Code generation, no reflection
■ Endpoint pipelining
■ Dead steps elimination
○ Better APIs
○ Better defaults
○ Small footprint
○ Dev UI support
● Great in conjunction with Mutiny, the Vert.x reactive SQL clients and
Hibernate Reactive!
But is it hard to make my endpoint faster-than-light?
Demo Time!
Recap
● Import quarkus-resteasy-reactive*
● Non-blocking by default
○ Also supports blocking use-cases: use @Blocking
● Faster by default
○ If you don’t need more speed, perhaps you need the usability improvements?
● We’re looking for feedback, so don’t hesitate to throw some our way!
● Get quarkus-resteasy-reactive for free today with the #RROSS
coupon
○ Offer good forever
■ There’s no fine print
● Well there is but it’s just a joke
This slide intentionally left plank

RESTEasy Reactive: Why should you care? | DevNation Tech Talk

  • 1.
    RESTEasy Reactive :why should I care? Stéphane Épardaud, Red Hat. @UnFroMage
  • 2.
    We always needa plan, even if we don’t follow it ● A brief glimpse at why you should care about async, reactive, blocking ○ And all those event-loop, IO Thread, Worker Thread terms that hipsters and C programmers use ● How can I turn my REST endpoints from rusted, slow, old-style to golden buzzword-enabled syrup? ○ DEMO!!! ● This item was placed here just to check if anybody is reading this, but it doesn’t matter we won’t have time to cover it anyway ● Recap and Questions
  • 3.
  • 4.
    Traditional architecture: IOand worker threads
  • 5.
  • 6.
  • 7.
    More efficient architecture:non-blocking by default
  • 8.
    A truly modernarchitecture
  • 9.
    So what isRESTEasy Reactive? ● JAX-RS implementation redone from scratch (client and server) ● Built for Quarkus ○ Async by default, using Vert.x ○ Reactive support with Mutiny ○ Ultra-fast architecture ■ Code generation, no reflection ■ Endpoint pipelining ■ Dead steps elimination ○ Better APIs ○ Better defaults ○ Small footprint ○ Dev UI support ● Great in conjunction with Mutiny, the Vert.x reactive SQL clients and Hibernate Reactive!
  • 11.
    But is ithard to make my endpoint faster-than-light?
  • 12.
  • 13.
    Recap ● Import quarkus-resteasy-reactive* ●Non-blocking by default ○ Also supports blocking use-cases: use @Blocking ● Faster by default ○ If you don’t need more speed, perhaps you need the usability improvements? ● We’re looking for feedback, so don’t hesitate to throw some our way! ● Get quarkus-resteasy-reactive for free today with the #RROSS coupon ○ Offer good forever ■ There’s no fine print ● Well there is but it’s just a joke
  • 14.