| Re: [jaxrs-dev] Guidance for adoption of Reactive APIs |
| Hi James, Thanks for sharing your work here. Let me start with a quick summary about the JAX-RS discussions we had during 2.1: (i) As you know, most JAX-RS use cases involve the return of a single value, an entity. Thus, support for CompletionStage was a natural extension to the API. (ii) We discussed the use of Flow in the context of SSE. As I recall, there were two issues with it: (1) we could not depend on JDK 9 (as you discuss in your document) and (2) the resulting API, unsurprisingly, felt a bit “generic”. (iii) There are other cases in JAX-RS were reactive streams could be of use (e.g., StreamingOutput) but these are very uncommon. Reactive streams are a much better fit in Web servers (Web sockets) and other “lower-level" APIs. In light of this, I’m curious about how you envision adoption of reactive APIs in the current MP stack where REST and JAX-RS are at the core of application development. Is it primarily via a future messaging API? Or some other API? — Santiago
|