Introduction
Overview
Nexaa Cloud Databases provide managed MySQL and PostgreSQL instances within your cloud environment, freeing you from the operational overhead of managing and maintaining your own database infrastructure. You can choose between 1-node, 2-node, or 3-node configurations depending on your performance and availability needs.
All databases are deployed inside a Namespace, and can only be accessed by containers within the same Namespace. External database access is currently not supported.
Key Concepts
Namespace-Scoped Access
Cloud Databases must be deployed within a Namespace. Only containers running in the same Namespace can connect to the database. This ensures a secure, isolated network environment by default.
1-Node Database
- Purpose: Ideal for development and testing
- Availability: No failover support
- Storage: All data stored on a single instance
- Connectivity: Requires IP allowlisting of containers that should access the database
2-Node Database
- Purpose: For production environments that require basic failover
- Availability: Synchronous data replication between two nodes
- Failover: If one node fails, the second takes over automatically with zero downtime
- Connectivity: Data accessible via a single main IP address
3-Node Database
- Purpose: High-availability setups for critical workloads
- Availability: Triple-node replication with strong fault tolerance
- Resilience: Failure of a node has minimal to no impact on availability
- Reliability: Designed to maximize uptime and reduce risk of service disruption
Shared Responsibility Model
| Responsibility Area | Nexaa | Customer |
|---|---|---|
| Information and Data | ✅ | |
| Network Configuration | ✅ (network reliability) | ✅ (internal access and firewall settings) |
| Database Patching | ✅ | |
| Cluster Infrastructure | ✅ | |
| Operating System | ✅ | |
| Physical Infrastructure | ✅ |
!note Some features, including external connectivity and more advanced backup options, are planned for future releases. Stay tuned for updates.