Frequently Asked Questions - LavinMQ

LavinMQ is a high-performance message broker built for modern applications. It supports AMQP messaging and is designed to be easy to operate, resource-efficient, and capable of handling large numbers of connections and long queues.

LavinMQ and RabbitMQ both support AMQP and similar messaging patterns. LavinMQ focuses on simplicity, performance, and operational efficiency while also offering features such as persistent exchanges and replayable queues.

LavinMQ is a good choice when you need high throughput, low memory usage, long queue support, many concurrent connections, and simple operations.

Yes. LavinMQ is open source and can be self-hosted or run as a managed service through CloudAMQP.

LavinMQ supports AMQP 0-9-1, HTTP, MQTT, and WebSockets on both shared and dedicated CloudAMQP plans. It does not implement AMQP 1.0 or STOMP.

Yes. LavinMQ implements AMQP 0-9-1, allowing applications to use many existing RabbitMQ-compatible client libraries.

CloudAMQP provides fully managed messaging services, including both LavinMQ and RabbitMQ deployments across multiple cloud providers and regions.

Yes. CloudAMQP offers managed LavinMQ instances, allowing you to focus on building applications rather than operating messaging infrastructure.

Create a CloudAMQP account, select a LavinMQ plan, choose a cloud provider and region, and create your instance through the CloudAMQP console.

Yes. CloudAMQP offers LavinMQ through AWS Marketplace. After subscribing, you can create and manage LavinMQ instances through the CloudAMQP console.

CloudAMQP supports multiple cloud providers and regions. Available options may vary depending on the selected plan.

Teams allow multiple users to manage the same CloudAMQP resources. Team members can be assigned different roles and permissions depending on their responsibilities.

Yes. TLS can be used to encrypt traffic between your applications and LavinMQ.

For the certificates CloudAMQP servers use and their root CA, see How do I authenticate the identity of your server? in the CloudAMQP FAQ.

No. Direct SSH access is not provided for managed CloudAMQP instances.

CloudAMQP provides monitoring tools, metrics, dashboards, and alarms to help you track resource usage and broker health.

Yes. LavinMQ supports both exchange federation and queue federation.

Applications can be separated using virtual hosts (vhosts), allowing independent queues, exchanges, users, and permissions within the same broker.

Availability options depend on your selected deployment plan and infrastructure configuration. Refer to the plan details and documentation for current capabilities.

Billing is based on the selected plan and usage. Charges are typically prorated based on how long an instance has been active.

CloudAMQP supports major credit cards, invoicing options, and marketplace billing where available.

Instances can be deleted through the CloudAMQP console. Deleting an instance permanently removes associated queues, exchanges, and stored data.

After all instances have been removed and any outstanding invoices have been settled, team accounts can be deleted through the CloudAMQP console.