RabbitMQ
RabbitMQ is a message broker for queueing, pub/sub, and streaming-style application integration. It is a good fit for asynchronous processing, worker pipelines, and service decoupling.
| Property | Value | Notes |
|---|---|---|
| Provider name | rabbitmq | Use this in landscape provider definitions. |
| Version | v0 | Current schema version exposed by the provider. |
| Category | Message Queue | Shown in the managed services catalog. |
| Scope | global | Available at team scope rather than being tied to a single workspace runtime. |
| Team singleton | false | Teams can create multiple RabbitMQ service instances. |
| Pause support | false | This provider does not support pausing. |
Closed testing
This provider is currently in an early testing state and is only available on dedicated installations (closed testing). The provider is still evolving, its schema, plans, and behavior may change in the future.
Schema
Config
| Field | Type | Required on create | Notes |
|---|---|---|---|
version | string | No | RabbitMQ server version. Default and only allowed value: 4.3. |
Secrets
| Field | Type | Required on create | Notes |
|---|---|---|---|
superuserPassword | string | Yes | Password for the administrative user. The username is always admin. |
Details / Output
| Field | Type | Availability | Notes |
|---|---|---|---|
host | string | Exposed after provisioning | Internal service hostname. |
port | integer | Exposed after provisioning | AMQP port, typically 5672. |
managementPort | integer | Exposed after provisioning | Management UI port, typically 15672. |
replicas | integer | Exposed after provisioning | Reported number of replicas. |
readyReplicas | integer | Exposed after provisioning | Number of replicas currently ready. |
ready | boolean | Exposed after provisioning | Indicates whether the cluster is ready. |
Plans
The provider exposes multiple plans: Small (id: 0), Medium (id: 1), and Large (id: 2).
Example plan: Small (id: 0).
| Parameter | Type | Default | Minimum | Maximum | Static | Notes |
|---|---|---|---|---|---|---|
storage | integer | 1024 | 1024 | - | No | Priced as storage-mib. |
cpu | number | 5 | - | - | No | Priced as cpu-tenths. |
memory | integer | 512 | - | - | No | Priced as ram-mib. |
replicas | integer | 1 | - | - | No | RabbitMQ node count in the example plan. |
Example in a Landscape
schemaVersion: v0.2
run:
broker:
provider:
name: rabbitmq
version: v0
plan:
id: 0
parameters:
storage: 1024
cpu: 5
memory: 512
replicas: 1
config:
version: "4.3"
secrets:
superuserPassword: "${{ vault.rabbitmqSuperuserPassword }}"
Other runtimes can use host and port for AMQP client connections, and managementPort for the management UI or API.
Authenticate with the username admin and the stored superuserPassword.
The same internal service endpoint is reachable from other Codesphere runtimes, including reactives, managed containers, and Virtual Cluster workloads.