Handling runtime failures
Quickbase uses several measures to achieve high-reliability and high-availability.
Redundancy of the runtime environment
Quickbase maintains production-ready compute capacity for all core infrastructure components within each location.
Runtime or application failures
If a runtime instance gets into an unhealthy state:
- The control plane automatically detects the issue.
- Quickbase automatically migrates applications pinned to that instance to other runtime instances.
- No action is necessary by customers, and they will not even be aware if such a migration occurs.
Disaster recovery
Quickbase maintains multiple geographically diverse hosting regions. All necessary data is continuously replicated across regions. In the event of one region's complete failure, we can quickly switch over and run from another region instead. We routinely switch between hosting locations multiple times per year to exercise our switchover capability.
The details behind our approach to disaster recovery depend on the hosting platform:
- Amazon AWS: Quickbase uses cloud architecture best practices, and we design our services to run active/active across multiple availability zones within a region.
- Google GCP: Quickbase uses cloud architecture best practices, and we design our services to run in a high availability configuration.
To better understand Quickbase’s RPO and other relevant details, please visit the Quickbase Trust Center.