Handling runtime failures

Quickbase is a high reliability and availability platform. There are a number of measures used to achieve this:

Redundancy of the runtime environment

A Quickbase data center contains many machines, each running multiple instances of the Quickbase runtime environment.

Runtime or application failures

If a runtime instance gets into an unhealthy state, the control plane will automatically detect this. Applications pinned to that instance are automatically migrated to other runtime instances, without any action necessary by customers, or even being aware of it.

Disaster recovery

Quickbase maintains multiple different, physical data centers, geographically dispersed. All necessary necessary information is continuously replicated across data centers. In the event of a complete data center failure, we have the capability to switch over and run from another data center. To better understand Quickbase’s RPO and other relevant details, please visit the Security & Compliance page.

The details behind this depend on the hosting platform:

  • Co-located data center: Quickbase runs multiple data centers. At all times, one is active and replicating out to the other passive data centers. Quickbase switches between data centers throughout the year to ensure reliability and test our capabilities.
  • AWS: Quickbase uses cloud architecture best practices and design our services to run active/active across multiple availability zones within a region.
  • Google: Quickbase uses cloud architecture best practices and design our services to run in a high availability configuration