Is your feature request related to a problem? Please describe.
The Azure SDK for Java supports a ServiceBusSenderAsyncClient and a ServiceBusReceiverAsyncClient that allows the use of reactive programming. However, the ServiceBusProcessorClient is still only synchronous.
Describe the solution you'd like
It would be nice for the Processor to accept an async message handler so that it can await responses on more expensive operations such as I/O.
Describe alternatives you've considered
Today I have to roll my own. I basically spawn an async client and define the Flux handler myself - meaning I have to support things like auto-recovery, spawning a new thread, etc. on my own, where it's much easier for me to get something wrong and miss a core part of what a Processor should be doing.
Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
Is your feature request related to a problem? Please describe.
The Azure SDK for Java supports a ServiceBusSenderAsyncClient and a ServiceBusReceiverAsyncClient that allows the use of reactive programming. However, the ServiceBusProcessorClient is still only synchronous.
Describe the solution you'd like
It would be nice for the Processor to accept an async message handler so that it can await responses on more expensive operations such as I/O.
Describe alternatives you've considered
Today I have to roll my own. I basically spawn an async client and define the Flux handler myself - meaning I have to support things like auto-recovery, spawning a new thread, etc. on my own, where it's much easier for me to get something wrong and miss a core part of what a Processor should be doing.
Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report