AMQP 1.0 support in Service Bus not working with Proxy. Enabled the proxy in the app.config with no luck. Able to communicate with Servicebus thorugh proxy while accessing queues with Azure SDK.
Related
Azure EventHubs (on tier standard) allows you to use the Kafka SDK. Does Azure Service Bus has a similar feature for RabbitMQ given that both work with AMQP?
I need to know basic difference between rabbitmq and "compose for rabbit" as a service in IBM cloud.
There is only one production-level RabbitMQ service in the IBM Cloud catalog: Compose for RabbitMQ.
The other service, rabbitmq, is an old, deprecated, experimental service that was part of Cloud Foundry. It should not be used and when you click it, it should redirect you to the Compose for RabbitMQ service.
I am looking in for the best way to implement the RabbitMQ consumer by using .Net Client which should be run as windows service.
I referred the RabbitMQ documentation and found the way to consume messages by using .Net client (https://www.rabbitmq.com/tutorials/tutorial-one-dotnet.html).
My current scenario is like, RabbitMQ is installed in AWS VM machine. I have to install dotnet client consumer service resides in On-premise network which should consume messages.
Which one is the best way, to always listen the Queue (AMQP protocol) or HTTP API which should get messages on demand (https://pulse.mozilla.org/api/).
Please advise.
Thanks,
Vinoth
I believe the answer is "neither." You should have your message queue as a back-end service behind the firewall, and expose your application functionality through a set of carefully-specified web services. The web services, which are exposed through the firewall but can communicate to services behind the firewall, would produce messages that would be transmitted to the server. Any services needing to produce or consume messages would need to do so via the web services, which would perform safety/security checking prior to forwarding the request on to the AMQP server.
If you need to expose AMQP directly to clients (i.e. that is the purpose of your app), then the recommendation is to do so via STOMP. I think a valid use case for exposing AMQP directly over the internet would be a rare thing to come across. The security implications of doing so would be immense.
My message-queue is managed by IBM WebSphere MQ and I would like to be able to listen for new enqueued messages using a WCF service.
Each new message should trigger a call to my service with the new message as a parameter.
Do you know any way about how to create such a service and host it?
If you are using WebSphere MQ v701 or above, then you can use the WebSphere MQ Custom channel for WCF. Using the custom channel you can build and host services. You can find more details and samples here
WMQ WCF based service can be hosted as a Windows service or a standalone application. It does not yet have capability to be hosted in an IIS or Windows Application Fabric/WAS.
We are implementing a service/message-bus feature in our SignalR application and have been looking at Redis, with automatic fail-over using Redis Sentiel. We would like to maintain our own servers and have read SignalR powered by Service Bus. Since this is a Winddows Azure implementation, how can I accomplish this in our internal network with VM's with automatic fail-over similar to the Redis solution discussed above?
You may want to look at Service Bus for Windows Server:
http://msdn.microsoft.com/en-us/library/windowsazure/jj193022(v=azure.10).aspx
It has API symmetry between Azure Service Bus and the Windows Server API (particularly for messaging: queues and topics/similar to SignalR). It doesn't include the caching and ACS services. However, if you want the Azure Service Bus - Caching...you can get that in:
AppFabric for Windows Server
http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx