Introduction
Overview
Nexaa provides RabbitMQ message queue instances within your cloud environment, allowing you to decouple and scale your applications effectively. With managed RabbitMQ services, you can focus on building your applications without worrying about the complexities of message queue management.
Key Concepts
Namespace-Scoped Access
Message Queues must be deployed within a Namespace. Only containers running in the same Namespace can connect to the message queue. This ensures a secure, isolated network environment by default. If you would like to externally connect to your message queue, please refer to the message queue connection guide.
We offer two configurations to suit different needs:
Single-Node Message Queue
- Purpose: Suitable for development and testing environments.
- Availability: Operates on a single node without failover support.
High-Availability Message Queue
- Purpose: Designed for production environments requiring high availability and fault tolerance.
- Availability: Consists of multiple nodes with data replication to ensure continuous operation.
- Resilience: In the event of a node failure, other nodes take over automatically, minimizing downtime.
Shared Responsibility Model
| Responsibility Area | Nexaa | Customer |
|---|---|---|
| Information and Data | ✅ | |
| Network Configuration | ✅ (network reliability) | ✅ (internal access and firewall settings) |
| Message Queue Patching | ✅ | |
| Cluster Infrastructure | ✅ | |
| Operating System | ✅ | |
| Physical Infrastructure | ✅ |
Note
Some features are planned for future releases.
Stay tuned for updates and enchantments or suggest your own in our feedback tool.