App service

RabbitMQ service

RabbitMQ message broker service for AMQP queues, event-driven workloads, and asynchronous service communication.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

All services

Why teams use this service

Technical profile

Review versions, ports, source, and packaging.

Stacks that use it

See where this service fits in ready-made stacks.

Runtime wiring and defaults

See ports, links, storage, configs, and runtime behavior.

Overview

Technical profile and packaging

This page shows how RabbitMQ is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

4.3, 4.2

Source repository

wodby/service-rabbitmq

Public Helm chart

wodby/rabbitmq

Ports and protocols

5672/TCP, 15672/HTTP, 15692/HTTP

Labels

rabbitmq, amqp, message-broker

Persistent volumes

Data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include RabbitMQ as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

RabbitMQ

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

5672/TCP, 15672/HTTP, 15692/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Volumes

Data