[beta] Hydra supports scaling up to 4 replicas of your database.
Hydra employs light weight compute orchestration so read-only users can avoid resource contention. Read scaling replicas will transparently access up to 4X compute resources to better handle concurrent query workloads. The result is an improved end user experience on your analytics schema. When connecting with a read scaling replica, each concurrent end user connects to a read scaling replica of the database that is served by its own process. Beyond this limit, applications can gracefully degrade by having multiple end users be served by the same process.​

​
Create read scaling replicas

To add read scaling replicas to your project please email support@hydra.so.

​
​Permissions and limitations

A read scaling replica is for read operations, such as querying tables, but restricts write operations, including:
  • Updating tables
  • Creating new databases​​

​
How a client uses read scaling replicas

When a client connects to Hydra with a read scaling replica:
  • It is assigned to one of the read scaling replicas for the user account.
  • This is in addition to the standard read-write processing that is used normally.
These replicas are eventually consistent, meaning data from read operations may briefly lag behind the latest writes.