Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

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

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

Descargar para leer sin conexión

There's a new version of RESTEasy tailor-made for Quarkus, but why was it created? What's so special about it? Why should you care? We will explain why reactive and async programming matter for performance and how you can take advantage of that to get outstanding performance with RESTEasy Reactive. We will even throw in some Hibernate Reactive for good measure during the demo. Don't care about performance? Don't worry. With its demonstrated ease of use and usability improvements, you will want to start using RESTEasy Reactive on your existing applications.

There's a new version of RESTEasy tailor-made for Quarkus, but why was it created? What's so special about it? Why should you care? We will explain why reactive and async programming matter for performance and how you can take advantage of that to get outstanding performance with RESTEasy Reactive. We will even throw in some Hibernate Reactive for good measure during the demo. Don't care about performance? Don't worry. With its demonstrated ease of use and usability improvements, you will want to start using RESTEasy Reactive on your existing applications.

Más Contenido Relacionado

Más de Red Hat Developers

Audiolibros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo

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

  1. 1. RESTEasy Reactive : why should I care? Stéphane Épardaud, Red Hat. @UnFroMage
  2. 2. 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
  3. 3. Alright, why should I care?
  4. 4. Traditional architecture: IO and worker threads
  5. 5. But… they’re all sleeping???
  6. 6. User
  7. 7. More efficient architecture: non-blocking by default
  8. 8. A truly modern architecture
  9. 9. 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!
  10. 10. But is it hard to make my endpoint faster-than-light?
  11. 11. Demo Time!
  12. 12. 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
  13. 13. This slide intentionally left plank

×