Using external message broker as commands' queue #8771
slawomirpiotrowski
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There is a problem with commands queue in Orleans. If destination silo fails for whatever reason than commands in it's queue get lost.
I wonder if it would be possible to implement a configurable queue providers? Current implementation could be the default "in memory queue".
This way it should be possible to use external message brokers as message queue implementation. Some brokers are fault tolerant so messages shouldn't be lost in case of silo failure - just another silo would activate destination grain and subscribe to existing queue of awaiting commands. It could use rabbitmq or azure service bus or just use an abstraction layer like masstransit so any broker could be easily used.
Beta Was this translation helpful? Give feedback.
All reactions