Message Brokers
Managed message brokers
NATS, RabbitMQ and Kafka on a server of their own in your private network, set up and updated by us.
What a broker is
Each broker runs on its own virtual machine in your private network, on the storage our databases use. Your services reach it by its private address.
Pick the engine your code already speaks. The panel is the same for all three: users, metrics, logs and plan changes.
Engines
NATS
Messages between services. JetStream keeps streams on disk. Clients for Go, Python, Node.js and others.
RabbitMQ
Queues for background jobs. Works with Celery, Laravel queues and any AMQP client.
Kafka
Event streams kept on disk for as long as you set. Works with any Kafka client.
What you get
Less maintenance
Setup and updates of the broker are on us.
Private by default
The broker is reached from your private network. Public access is a switch in the panel, behind your security group.
Fast disk
Streams and queues are written to the storage our databases use, about 150 µs per fsync.
Room to grow
Move to a bigger plan when traffic grows.
Questions
Is my broker shared with other customers?
No. Each broker runs on its own virtual machine in your private network, and no other customer uses it.
Can I reach it from the internet?
Only when you switch public access on in the panel, and then through your security group.
How do my applications log in?
With users you make in the panel, each with its own rights.
What do I see in the panel?
The broker's metrics and logs, its users, and its plan.