Forge SQL offers a multi-tenant SQL solution offering tenant isolation and stable query performance. To do so, we add a few constraints over and above TiDB's limitations:
Foreign keys are not supported. You can still perform JOIN operations, but DELETE operations will not be cascaded.
Each SQL statement can only contain a single query.
The following limits also apply:
The following limits are applied to your app's Forge SQL usage on a per-install basis:
| Resource | Limit |
|---|---|
| Total stored data | 1 GiB (production installs) |
256 MiB (staging installs) | |
128 MiB (development or custom environment installs) | |
| Number of tables | 200 |
| DML Requests per second (RPS) | 150 |
| DDL Requests per minute (RPM) | 25 |
| Size per row | 6Mib |
| Total query execution time for all current invocations | 62.5 seconds (within each minute) |
App databases provisioned and managed via Forge SQL are backed up periodically.
The following limits apply to each query sent and response received by your app's Forge SQL database functions:
| Resource | Limit |
|---|---|
| Memory usage per query | 16 MiB |
| Query time per minute (s/minute) | 62.5 seconds |
| Request size | 1 MiB |
| Response size | 4 MiB |
Per-connection timeout for SELECT queries | 5 seconds |
Per-connection timeout for INSERT, UPDATE, and DELETE queries | 10 seconds |
| Per-connection query timeoutfor DDL queries | 20 seconds |
Forge SQL has not yet undergone external assessment for SOC 2 or ISO certification. As we continue development on Forge SQL, we will aim to include it in our standard audit certification reporting cycle.
If you add Forge SQL to an existing app, admins of that app's current installations must review and consent before updating.
As such, adding Forge SQL to an existing app will require a major version upgrade. This will be triggered through the sql module (which is required to enable Forge SQL on an app).
Rate this page: