Skip to main content

MassTransit–Using RabbitMQ Virtual Hosts

Today I want to talk about a specific feature in RabbitMQ and how we can use this feature with my favorite messaging library MassTransit.

Virtual Hosts

With virtual hosts you can create a logical grouping in  your RabbitMQ cluster. Every exchange, queue, binding, user permissions, and so on is bound to a specific virtual host and isolated from the other virtual hosts. This helps to avoid naming collisions.

There is always at least one virtual host in use; the default one is ‘/’.

To create a new virtual host in your RabbitMQ cluster, you can use the rabbitmqctl's add_vhost command:

rabbitmqctl add_vhost development

Or you can use the RabbitMQ Management portal:

  • In the Management Portal go to the Admin tab and click on the Virtual Hosts section on the right:

  • Go to the Add Virtual Host form and enter a name and an optional description and tags:

  • Click on Add virtual host to create the new virtual host.

Remark: Be aware that virtual hosts are a security boundary, so I would recommend to create different users per virtual host.

Using Virtual Hosts in MassTransit

Now that we have a new Virtual Host created, let’s see how we can use this in MassTransit.

Let’s have a look at a simple example from the MassTransit documentation:

In the example above, the virtual host is passed as a second parameter after the servername in the Host() method:

You can also specify it through the URI:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...