All Timescale Cloud services are offered at multiple configurations which are defined as plans. The plan usually determines the number of VMs the service runs in, the high-availability configuration, number of CPU cores and size of RAM and storage volumes.
- Basic Plans: include 2 days of backups and automatic backup / restore upon instance failure.
- Pro Plans: include 3 days of backups and automatic failover to a hot standby
- Dev Plans: include 1 day of backups and automatic backup / restore upon instance failure
A plan can be upgraded while the service is running with minimal disruption. The service is reconfigured to run on larger VMs in the background and once the reconfiguration is complete the DNS names the service uses are pointed to the new hosts. This will cause a minimal disruption while DNS changes are propagated.
The service availability is based on the service type and plan being used.
- Basic & Dev Plans: have limited capabilities when the single node fails.
- Pro Plans: are resilient to single node failures.
Our Basic & Dev plans are serviced by a single Virtual Machine node. This means that if the node fails, the service will be unavailable until a new VM is built. There may be some degree of data loss as it is possible that some of the latest changes to the data haven't been backed up before the failure. It can also take a long time to recover the service back to normal operation as a new VM needs to be created and restored from backups before the service can resume operations. The time to recover depends on the amount of data to restore.
Our Pro plans are very resilient to failures. A single node failure will cause no data loss and the possible downtime will be minimal. In case an acting TimescaleDB master node fails an up-to-date replica node is automatically promoted to become the new master. This will cause minimal outage to applications as they need to reconnect to the database to access the new master.
Finally, there are four levels of plan types available:
- IO-Optimized and Compute-Optimized: These configurations are optimized for IO performance with the storage using SSDs (which are better suited for IOPs).
- Storage-Optimized: These configurations typically have larger amounts of overall storage using HDDs.
- Dev-Only: These configurations are typically smaller footprints (for low cost) designed for development / test scenarios.