Hello everybody,
Reading documentation and playing around with code I got couple questions that, I believe, you can help me with:
1. Azure Service Bus has separate permissions set for shared keys. Is it possible to give a mass transit receiving endpoint read-only access to Azure Service Bus?
Now when I tried to connect with read-only shared key, mass transit said that it needs management permissions.
2. If I got saga pattern right, main responsibility of saga is to coordinate and correlate events in a distributes app. Am I right with idea that when saga reacts on incoming message it fires a command to a queue for processing. With that in place saga receiving queue should be different, right?
This is how I understand flow and setup (see attached draft picture).
- Saga is registered on receiving endpoint on queue "saga_queue". For instance saga coordinates two data processing steps: Processor A and Processor B. When saga is initialized it should send processing command to queue "a_processing_queue".
- When processing A is done, sage translates to another step and kicks processing B.
- Auto-scaled set of Processors A are receiving on queue "a_processing_queue".
- When processor A done with a task it publishes event "Processor A is done with the task".
- A event it would be received on all endpoints. Saga instance will react on this event.
- With this step Saga will send command to "b_processing_queue".
- When Data Processor B is done with processing it publish "Processor B is done with the task" event.
- Saga reacts on the event, translates to final step.
Please let me know if this does not make sense, or if I got the thing wrong.

Regards,
Dmytro