A cool feature of Quarkus is that you can mix both synchronous and asynchronous paradigms and don't have to commit to just one. This can be very useful, for example, if you want to parallelize REST calls to third-party APIs in an otherwise synchronous backend.
Having migrated to RESTEasy Reactive sporadic SocketExceptions occurred in one of our AWS Lambdas several minutes after the actual Lambda execution. This article describes one possible solution for this problem by disabling the connection pool for the used REST client with the help of custom HttpClientOptions but of course with the price of a lower overall performance.
Until Quarkus 2.8 RESTEasy Classic was the default JAX-RS implementation when using REST in a Quarkus project. Then they switched over to RESTEasy Reactive, which is the reactive version but also contains the classic blocking flavor. This post summarizes my experiences with the migration to RESTEasy Reactive.