Already running one of these brokers? Point your existing client at KubeMQ instead of rewriting it — change one connection string (or set an environment variable), keep your code, and your app keeps speaking the same wire protocol it already speaks.

Pick your broker

Kafka

Repoint bootstrap.servers at KubeMQ's embedded Kafka engine — native clients connect unchanged.

RabbitMQ

Swap the AMQP 0-9-1 connection string — exchanges, queues, and bindings carry over.

AWS SQS & SNS

Point the AWS SDK or CLI at KubeMQ's drop-in SQS/SNS endpoint — no rewrite.

MQTT

Change the broker host — MQTT 3.1.1 and 5.0 clients connect unchanged.

Google Cloud Pub/Sub

Set PUBSUB_EMULATOR_HOST — an unmodified Pub/Sub client publishes and pulls.

STOMP

Change the STOMP broker host — every destination type maps.

JMS

Swap your JMS ConnectionFactory to Apache Qpid JMS over KubeMQ's AMQP 1.0 connector.

ActiveMQ

Java/JMS apps ride AMQP 1.0; non-Java apps repoint over STOMP or MQTT instead.

AMQP 1.0

Point a native AMQP 1.0 client — go-amqp and others — at KubeMQ; queues, topics, and RPC all map.

Drop-in levels

Each card above states its drop-in level — how much application change the move requires: endpoint-only — change the host/port or an env var; client + code unchanged. client-swap — swap the client library; app code mostly unchanged. partial-rewrite — some app-level changes beyond the client/endpoint.

Full definitions and the cross-protocol matrix live in the migration hub.

Replace your messaging stack