Running RabbitMQ with Docker

Short post today, mostly just wanted to how to setup RabbitMQ for local development. Refer back to my previous post to learn more about RabbitMQ.

Prerequisite
For complete guide reference, check out the Docker Hub Website for RabbitMQ.

Why use Docker?

Before starting my current job at iHerb, I would go straight for the Windows installation (my development environment) for all of my development tools needs. It was straight forward and "just worked" a lot of the time.

What I've begun to realize experimenting with all these different tooling and services is that things can get a bit cluttered, you will have a bunch of supporting systems that need to be run - caches, queues, databases and it can be a hassle to manage them through window services and executables. Additionally some of these require additional dependencies outside of the executable itself, which prompts you to install even more tooling.

The great thing about docker is that it defines a pre-built environment that has all of the dependencies needed, as well as keeps itself isolated to a non-user defined space, separating out your usual work space from your tooling work space.

You have complete control to start/stop various tools from the command line, making it great way to manage these services.

Installation

First we'll need to create the container for RabbitMQ. I'm choosing the version that contains the management plugin, which has a UI to manage the rabbitmq service.

Run the command:
docker run -d -p 5672:5672 -p 15672:15672  --name rabbitmq rabbitmq:3-management

  •  docker run - The command used to declare that you want to create a new container
  • -d - The new container will run in detached mode, or that it is not tied to the command line
  • -p 5672:5372 - Opening the port to localhost to be used for messaging
  • -p 15672:15672 - Opening the port to localhost to be used for the management UI
  • --name - The docker name of the container
  • rabbitmq:3-management - The name of the image to be pulled (rabbitmq is the repository, and 3-management is the tag)

Using the Management UI

Once your container is running, you should be able to navigate to the RabbitMQ UI to opening up your browser and going to http://localhost:15672/

It should look something like this:


Source

Starting the Container Again

There may be a time when your container may stop due to a restart or some other circumstance.

You should be able to run it again with the command:
docker start <container name>


And that's it! You should now have a working RabbitMQ service running through Docker.

Comments

Post a Comment

Popular posts from this blog

Uncle Bob's Clean Architecture

Image
The basis of my current understanding of architecture comes from the brilliant mind of Robert C. Martin (Uncle Bob). You can find the original post through his blog , which I strongly encourage you to read. In this post I'll try to summarize some of the key points I've understood from his post. Clean Architecture Source Clean architecture is a design used to emphasize the structure and relation of your various code components to promote the idea of Dependency Rule , such that "source code dependencies only point inwards" . Clean architecture is able to promote this by defining that your software system consists of various layers , that can be organized in such a way that the layers point in one direction, and a dependency graph will not have circular reference. The reason this is important is because it allows you to keep closely code related, and increase clarity of how components fit into your system. Explaining the Layers We can really separate out this
Read more

C4 Model: Describing Software Architecture

Image
The point behind a presentation of Visualizing Software Architecture , by Simon Brown, was that we need to standardize the way software developers communicate with each other in respect to our discussions of software architecture. As part of Simon's consultation, one exercise he gave to software architects was a simple task to white board the architecture of a software system. The results he received varied immensely, and there was never a defacto standard format that he received from this exercise. When inspecting the feedback from the participants, the general answer was that it was easy to come up with the design, but difficult to properly put their ideas onto paper, or white board in this case. White Board Example, c4model.com Simon sought to start a movement by defining a set of organizational rules to help us describe our software architecture with a set of standard terminologies. His work has let to C4 Model , which stands for C ontext, C ontainers, C omponents,
Read more

Multi-Tenant Design: The Basics

Image
As your software system begins to grow and become a successful, you may find yourself at a place where you will want to monetize your software by allowing other companies to use it. One such design that will come in handy is called the Multi-Tenant design, and it allows you to license your software to other companies, allowing them to use your software system for through some contract. You manage the system, and they are merely an entity within it, a tenant. Source At its core, a multi-tenant design is driven by the idea that each tenant contains an identifier, which is then passed through with each request or action. By including this information, the system will know what behavior or data set to pull from. Traditionally the tenant identifier is GUID  that is transferred through HTTP requests as a HTTP header, x-tenant-id . The value is then kept within the thread context, and used to determine the configuration of a request, as well as the data it can access. Data should ei
Read more