Legacy Product Notice
This article applies only to the Version 1 (Legacy) Cloud Database product.
For the latest Cloud Database documentation (V2), API references, and features, please visit our new documentation portal at: docs.nexaa.io/cloud-database.
This article applies only to the Version 1 (Legacy) Cloud Database product.
For the latest Cloud Database documentation (V2), API references, and features, please visit our new documentation portal at: docs.nexaa.io/cloud-database.
Tilaa Managed Cloud Database (V1) allows you to run MySQL or PostgreSQL clusters without worrying about the underlying hardware or operating system updates. We manage the uptime; you manage the data.
Cluster Architectures
Depending on your needs, V1 databases are available in three configurations:
-
1 Node (Standalone):
- Best for: Development, Testing, Staging.
- Redundancy: None. If the node fails, the database is offline.
-
2 Nodes (High Availability):
- Best for: Production websites.
- Redundancy: Master-Slave replication. If the primary node fails, the secondary node takes over automatically with zero downtime.
-
3 Nodes (Maximum Availability):
- Best for: Mission-critical applications.
- Redundancy: Distributed cluster with quorum. Provides the highest level of data integrity and uptime assurance.
Management & Responsibility
Because this is a managed service, the division of tasks is as follows:
- Tilaa: Manages the hardware, OS patching, database engine updates, and cluster uptime.
- Customer: Manages the database structure (Schema), SQL queries, and data integrity.
Manual Configuration Requests (Support)
The V1 platform does not yet have a self-service portal for configuration changes. To perform administrative tasks, please email support@tilaa.com.
You must contact Support for:
- IP Whitelisting: By default, the database is locked. You must provide us with the IP addresses of your application servers that need access.
- User Management: Creating new database users or resetting passwords.
- Scaling: Adding more RAM/CPU or upgrading from a 1-node to a 2-node cluster.
- Cancellation: Terminating the service.
Important Note on Backups (V1):
Automated backups are not included in the V1 product. You are responsible for creating your own SQL dumps or backups of your data.
Automated backups are not included in the V1 product. You are responsible for creating your own SQL dumps or backups of your data.