Skip to content

Commit ede5767

Browse files
authored
[Hyperdrive] explain d1 & hyperdrive (#21100)
* [Hyperdrive] explain d1 & hyperdrive * Update src/content/docs/hyperdrive/reference/faq.mdx
1 parent 1a29bea commit ede5767

File tree

1 file changed

+12
-0
lines changed
  • src/content/docs/hyperdrive/reference

1 file changed

+12
-0
lines changed

src/content/docs/hyperdrive/reference/faq.mdx

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,18 @@ Hyperdrive connects to your database using [Cloudflare's IP address ranges](http
1515

1616
You can use this to configure restrictions in your database firewall to restrict the IP addresses that can access your database.
1717

18+
### Does Hyperdrive support connecting to D1 databases?
19+
20+
Hyperdrive does not support [D1](/d1) because D1 provides fast connectivity from Workers by design.
21+
22+
Hyperdrive is designed to speed up connectivity to traditional, regional SQL databases such as PostgreSQL. These databases are typically accessed using database drivers that communicate over TCP/IP.
23+
Unlike D1, creating a secure database connection to a traditional SQL database
24+
involves multiple round trips between the client (your Worker) and your database server.
25+
See [How Hyperdrive works](/hyperdrive/configuration/how-hyperdrive-works/) for more detail on why round trips are needed
26+
and how Hyperdrive solves this.
27+
28+
D1 does not require round trips to create database connections. D1 is designed to be performant for access from Workers by default, without needing Hyperdrive.
29+
1830
## Pricing
1931

2032
### Does Hyperdrive charge for data transfer / egress?

0 commit comments

Comments
 (0)