Think of a repository where you are able to consume knowledge that someone shared as well as understand how it works. Does GitHub come to mind? What if you could do the same thing with deployment automation? ElasticBox boxes are your GitHub equivalent for sharing, running, and explaining deployment automation code. Read More
In my last two blog posts, I covered how to deploy a single RabbitMQ node for testing or non HA queues and RabbitMQ Cluster for HA queues.
In this blog post, I’ll cover the latest and the most reliable scenario, with a slight twist. The basic idea behind queue federation is to deal with load-balancing messages across queues on different brokers. If you have a set of queues federated with each other, then producers can publish into them and consumers can consume from them from any location. This time we’ll use Google Compute. Read More
In my last blog post, I showed how easy it is to deploy a single RabbitMQ node for testing or non-HA queues. In this scenario, we will deploy a cluster of 2 nodes. First, we need to create a wrapper Box built on top of RabbitMQ to create the cluster. Let’s call it RabbitMQ Cluster Node. Read More
As you know, ElasticBox provides one-click deployments of applications using Boxes. In this blog post, I will go over how to deploy RabbitMQ using ElasticBox in a few simple steps. When you sign into ElasticBox, you’ll see that we’ve already created a Box for you to use for this deployment.
What is RabbitMQ?
RabbitMQ is a complete and highly reliable enterprise messaging system based on the AMQP standard. It offers a variety of features to let you trade off performance with reliability, including persistence, delivery acknowledgements, publisher confirms, and high availability. Read More