Add more MQ options
Add more MQ Adapters, e.g: Rabbit MQ, Amazon SQS, Azure Service Bus, ZeroMQ/nanomsg.
Support for Azure ServiceBus was added in v4.5.14 in new ServiceStack.Azure NuGet package:
http://docs.servicestack.net/releases/v4.5.14#servicestackazure
Please create separate Feature Requests for other MQ brokers.
-
Jeff S commented
Also RackspaceCloud Cloud Queues. (They support pub/sub and producer/consumer queueing)
-
Wayne Brantley commented
Great, thanks. Can you consider handling the RPC model with this adapter (and the others)? I think that is very key.
-
ok added separate feature requests for:
Azure Service Bus: http://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/5470871-add-mq-server-support-for-azure-service-bus
-
Wayne Brantley commented
@Demis - perhaps you should break this feature request into on feature request for each MQ option? That way you can close the Rabbit one, open new Windows Service Bus, Azure, etc?
Also, maybe I should make my RPC its own item...?
-
Wayne Brantley commented
Thanks for your initial Rabbit MQ support.
I think you should support all 6 use cases of Rabbit out of the box. http://www.rabbitmq.com/getstarted.htmlSpecifically, the RPC scenario...a very common use case across all MQ agents. Something like this:
https://github.com/mikehadlow/EasyNetQ/wiki/Request-Response
Example use case:
Just like we can use RPC over JSON to a service stack service, we can insert RabbitMQ in the middle and have X servers pulling out and processing messages from the queue and replying back. -
Johann Klemmack commented
Consider Windows Service Bus (v1.1) as well as Azure Service Bus. Very similar API, but together they support a much broader set of use cases.
-
Nicklas Overgaard commented
+3 for the Azure Service Bus!
-
Michael Daly commented
+1 for AWS
-
Stefan Tsalapatis commented
RabbitMQ.
-
Alex commented
+1 for Rabbit
-
Dimitar commented
Definitely the RabbitMQ.