Skip to content

Commit 3c0c291

Browse files
Oxyjunvy-ton
andauthored
Update src/content/docs/d1/platform/limits.mdx
Co-authored-by: Vy Ton <[email protected]>
1 parent f0fac80 commit 3c0c291

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/d1/platform/limits.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Frequently asked questions related to D1 limits:
5151

5252
D1 is designed for horizontal scale out across multiple, smaller (10 GB) databases, such as per-user, per-tenant or per-entity databases. D1 allows you to build applications with thousands of databases at no extra cost for isolating with multiple databases, as the pricing is based only on query and storage costs.
5353

54-
- Each D1 database can store up to 10 GB of data, and you can create up to 50,000 separate D1 databases. This allows you to split a single monolithic database into multiple, smaller databases.
54+
- Each D1 database can store up to 10 GB of data, and you can create up to thousands of separate D1 databases. This allows you to split a single monolithic database into multiple, smaller databases, thereby isolating application data by user, customer, or tenant.
5555
- Scaling horizontally increases data isolation.
5656
- Queries on smaller databases execute faster.
5757

0 commit comments

Comments
 (0)