Nano.Eventing.RabbitMq 10.0.0-preview1

Nano.Eventing.RabbitMq

RabbitMq eventing for Nano applications.

Table of Contents

• Home
• Summary
• Registration
• Configuration
• Docker Compose
• Kuberentes

Summary

Eventing Provider implementation for RabbitMq.

📖 Learn more about Nano Eventing.
📖 Learn more about Nano Kubernetes RabbitMq.

Try it out yourself using the Api.Eventing.RabbitMq or Console.Eventing.RabbitMq example.

Registration

Install the Nano.Eventing.RabbitMq NuGet package.

dotnet add package Nano.Eventing.RabbitMq;

Continue with registering the RabbitMqProvider provider during application startup in the ConfigureServices(...) method.

...
.ConfigureServices(services =>
{
    services
        .AddNanoEventing<RabbitMqProvider>();
})
...

Configuration

Add the eventing configuration.

"Eventing": {
  "Host": null,
  "VHost": null,
  "Port": 5672,
  "Timeout": 30,
  "UseSsl": false,
  "Heartbeat": 60,
  "PrefetchCount": 50,
  "Credentials": {
    "Id": null,
    "Secret": null
  }
  "HealthCheck": {
    "UnhealthyStatus": "Unhealthy"
  }
}

Docker Compose

In addition to registering and configuring storage, you also need to configure your docker-compose setup. The rabbitmq image is the manangement image, so you are able to access the interface here: http://localhost:15672 and monitor and observe event messages being published and consumed.

services:
  {service-name}:
    depends_on:
      - eventing

  eventing: 
    image: rabbitmq:management
    hostname: rabbitmq
    ports:
      - 5671:5671
      - 5672:5672
      - 15671:15671
      - 15672:15672
    networks:
      - network
    environment: 
      RABBITMQ_DEFAULT_USER: rabbitmq_user
      RABBITMQ_DEFAULT_PASS: password
      RABBITMQ_DEFAULT_VHOST: "/"

Kubernetes

Next, add the following to your Kubernetes deployment.yaml or cronjob.yaml (depending on application type) for the Nano application.

spec:
  template:
    spec:
      containers:
        env:
        - name: Eventing__Credentials__Secret
          valueFrom:
            secretKeyRef:
              name: rabbitmq
              key: rabbitmq-password

You also need to map the rabbitmq secret that is created alongside the Nano Azure Kuberenetes Eventing in the deployment.yaml or cronjob.yaml for eventing authentication.

⚠️ The rabbitmq secret will be reused for all applications using RabbitMQ as eventing provider.
That makes it easy to change the secret values later on when needed, and just requires the secret values to be updated and re-deployed.