RabbitMQ is great for connecting critical systems to AMQP clients. But how do you connect to mobile and web clients for bi-directional messaging in a way that's secure, reliable, flexible, and scaleable?

What if you didn't want to open up your back-end servers to the net, but just wanted to continue communicating with RabbitMQ? What if you did not want to require clients to support any installables or require the latest web browsers or websockets technology?

I think we have the answer... use PubNub's open-source RabbitMQ adapter (https://github.com/pubnub/rabbitmq).

Your entire RabbitMQ deployment continues humming along just as it always did, with no changes. The PubNub RabbitMQ adapter will work as another AMQP client, and will connect to PubNub over standard http ports 80- and 443 (no special ports or firewall shenanigans required). The adapter will then publish/subscribe to PubNub as needed, while pushing/consuming to RabbitMQ.

You've now connected RabbitMQ to the web, without opening up your backend. The adapter can implement business logic to scrub data before publishing/subscribing, keeping the inbound and outbound data safe. You now support all web clients through PubNub, from the mobile clients to old, crusty web browsers.

The blog post url has code examples as well as video tutorials so you can see it in action. Follow the tutorial to get set up with your own web-connected RabbitMQ deployment, in as little as 10 minutes.