Nope

N

Nikil•10/7/23, 3:07 PM

So am I understanding Hyperdrive correctly? It's basically the same idea as Cloudflare DNS w/ CDN-style caching but for DBs? That sounds cool...

Kkian Nope

M

mattfreeman•10/9/23, 5:53 AM

Any plans for this? It would be awesome use case to connect into a zero trust with Cloudflare Warps for team, point DataGrip at the hyperdrive endpoint and presume it gets hyperdriven from a near edge, and enjoy the acceleration of less chat between me and live DB 300ms away.

K

kianOP•10/9/23, 7:04 PM

I don't think there's a timeframe on it hyperdrive

Kkian It'd be nice if Wrangler made a warning/error when you use local development w/ ...

K

kianOP•10/9/23, 7:06 PM

So it turns out the docs callout I was thinking of is actually in Workers AI, and there isn't one for Hyperdrive. Oops

Kkian Who will win, docs aside or https://github.com/cloudflare/workerd/pull/1266/

K

kianOP•10/9/23, 7:13 PM

My bets have shifted over to the PR now meowlul

K

kianOP•10/9/23, 7:14 PM

I guess docs asides are pretty easy to miss - it'd be cool for Wrangler to do the warnings (like it does for Queues in remote mode currently).

K

kianOP•10/9/23, 7:14 PM

I guess that's hard for remote mode which can support them independently of a new Wrangler release, but local should be fine.

M

Max (@rozenmd)•10/9/23, 7:16 PM

Converted the hyperdrive example to work with Hono if anyone's curious:

import { Client } from 'pg';
import { Hono, MiddlewareHandler } from 'hono';

type Bindings = {
    HYPERDRIVE: Hyperdrive;
};

const app = new Hono<{
    Bindings: Bindings;
    Variables: {
        DB: Client;
    };
}>();

const dbMiddleware: MiddlewareHandler = async (c, next) => {
    c.set('DB', new Client({ connectionString: c.env.HYPERDRIVE.connectionString }));
    await next();
};

app.get('/', dbMiddleware, async (c) => {
    try {
        // Connect to our database
        await c.var.DB.connect();

        // Test query
        let result = await c.var.DB.query({ text: 'SELECT * FROM pg_tables' });

        // Return result rows as JSON
        return c.json(result);
    } catch (e) {
        console.log(e);
        return Response.json({ error: JSON.stringify(e) }, { status: 500 });
    }
});

export default app;

import { Client } from 'pg';
import { Hono, MiddlewareHandler } from 'hono';

type Bindings = {
    HYPERDRIVE: Hyperdrive;
};

const app = new Hono<{
    Bindings: Bindings;
    Variables: {
        DB: Client;
    };
}>();

const dbMiddleware: MiddlewareHandler = async (c, next) => {
    c.set('DB', new Client({ connectionString: c.env.HYPERDRIVE.connectionString }));
    await next();
};

app.get('/', dbMiddleware, async (c) => {
    try {
        // Connect to our database
        await c.var.DB.connect();

        // Test query
        let result = await c.var.DB.query({ text: 'SELECT * FROM pg_tables' });

        // Return result rows as JSON
        return c.json(result);
    } catch (e) {
        console.log(e);
        return Response.json({ error: JSON.stringify(e) }, { status: 500 });
    }
});

export default app;

import { Client } from 'pg';
import { Hono, MiddlewareHandler } from 'hono';

type Bindings = {
    HYPERDRIVE: Hyperdrive;
};

const app = new Hono<{
    Bindings: Bindings;
    Variables: {
        DB: Client;
    };
}>();

const dbMiddleware: MiddlewareHandler = async (c, next) => {
    c.set('DB', new Client({ connectionString: c.env.HYPERDRIVE.connectionString }));
    await next();
};

app.get('/', dbMiddleware, async (c) => {
    try {
        // Connect to our database
        await c.var.DB.connect();

        // Test query
        let result = await c.var.DB.query({ text: 'SELECT * FROM pg_tables' });

        // Return result rows as JSON
        return c.json(result);
    } catch (e) {
        console.log(e);
        return Response.json({ error: JSON.stringify(e) }, { status: 500 });
    }
});

export default app;

import { Client } from 'pg';
import { Hono, MiddlewareHandler } from 'hono';

type Bindings = {
    HYPERDRIVE: Hyperdrive;
};

const app = new Hono<{
    Bindings: Bindings;
    Variables: {
        DB: Client;
    };
}>();

const dbMiddleware: MiddlewareHandler = async (c, next) => {
    c.set('DB', new Client({ connectionString: c.env.HYPERDRIVE.connectionString }));
    await next();
};

app.get('/', dbMiddleware, async (c) => {
    try {
        // Connect to our database
        await c.var.DB.connect();

        // Test query
        let result = await c.var.DB.query({ text: 'SELECT * FROM pg_tables' });

        // Return result rows as JSON
        return c.json(result);
    } catch (e) {
        console.log(e);
        return Response.json({ error: JSON.stringify(e) }, { status: 500 });
    }
});

export default app;

Note that I've renamed "client" to "DB", otherwise its the same

M

meai1•10/10/23, 2:52 PM

I keep getting " not_entitled [code: 10000]" even though I can connect to the db via datagrip just fine. Do I need to create a token permission for hyperdrive or do I need a paid workers plan? It logs me into cloudflare via oauth so I dont know what I'm not entitled for

Mmeai1 I keep getting " not_entitled [code: 10000]" even though I can connect to the db...

C

Cyb3r-Jak3•10/10/23, 2:53 PM

Workers paid plan is required for hyperdrive

M

meai1•10/10/23, 2:53 PM

oh okay, thank you

A

alex (he/him)•10/11/23, 6:39 PM

if hyperdrive keeps connections in a warm pool, does that mean that serverless dbs e.g. neon wouldn't suspend to not pay for compute?

U

Unsmart•10/11/23, 6:41 PM

If they charge by connection hours then I would assume that would be the case yes

K

kianOP•10/11/23, 6:41 PM

There's an initial connection timeout of 15 seconds and an idle connection timeout of 10 minutes.

K

kianOP•10/11/23, 6:42 PM

Neon's default auto-suspend delay is 5 minutes

K

kianOP•10/11/23, 6:42 PM

I imagine Hyperdrive might let you configure the timeout periods down the line

A

alex (he/him)•10/11/23, 6:42 PM

Ok that means neon will stay online 10 minutes instead of the 5 minutes?

A

alex (he/him)•10/11/23, 6:42 PM

Or are idle connection not forcing the db to stay online?

C

Colin•10/11/23, 10:52 PM

hey y'all - wanted to ask if anyone had opinions regarding Neon w/ Neon's connection pooling vs Neon w/ Hyperdrive (aside from the "one is GA and one isn't")

C

Colin•10/11/23, 10:53 PM

It seems like the main Hyperdrive-specific features are query caching + analytics (not yet but soon)

C

Colin•10/11/23, 10:54 PM

does anyone have experience with it / have any thoughts i might be missing?

CColin hey y'all - wanted to ask if anyone had opinions regarding Neon w/ Neon's connec...

I

Isaac McFadyen•10/11/23, 10:55 PM

Hyperdrive will be more efficient. The reason for that is:

Hyperdrive:
Worker --(very low latency)--> Hyperdrive --(persistent connection)--> Neon, so connection establishment from Worker to Hyperdrive is fast
Neon:
Worker --(higher latency)--> Neon Pooler, so while Neon might handle connection pooling the connections will still take a longer amount of time to start

Workers are rapidly spun up/down based on requests, so initial connection time is very important.

I

Isaac McFadyen•10/11/23, 10:56 PM

However, your Neon DB might not sleep very well with inactivity on Hyperdrive. See the conversation above.

IIsaac McFadyen Hyperdrive will be more efficient. The reason for that is: **Hyperdrive:** Work...

C

Colin•10/11/23, 10:58 PM

I definitely understand this for the

pg

pg

driver, but if we're using

@neondatabase/serverless

@neondatabase/serverless

or similar I'd expect their optimizations to reduce round trips would make it closer at least

C

Colin•10/11/23, 10:59 PM

i'm not sure how close that'd be to hyperdrive, if it's comparable at all

CColin I definitely understand this for the `pg` driver, but if we're using `@neondatab...

I

Isaac McFadyen•10/11/23, 10:59 PM

Ah - missed that you were using the Serverless driver. That should be fast to start since it's Websockets to the closest Neon node which then uses a long-lived TCP connection.

I

Isaac McFadyen•10/11/23, 11:01 PM

Check out https://neon.tech/demos/ping-thing if you want some preliminary numbers.

Ping Thing

A @neondatabase/serverless demo

I

Isaac McFadyen•10/11/23, 11:01 PM

In particular you want the Seconds field.

C

Colin•10/11/23, 11:03 PM

yep I totally forgot to mention the serverless driver, my bad. so probably a better way to phrase what I was asking about is "how should we expect hyperdrive w/ standard SQL drivers to perform in comparison to neon w/ serverless drivers"

C

Colin•10/11/23, 11:04 PM

it still seems like Hyperdrive might be faster as it's much closer to the worker despite having more round trips when establishing a connection(?)

C

Colin•10/11/23, 11:05 PM

but it seems like there's a lot of Neon fans in here who might've tried this instead of just me theorizing

CColin it still seems like Hyperdrive might be faster as it's much closer to the worker...

M

Matt Silverlock•10/12/23, 10:39 AM

The Neon Serverless driver still needs to make 3-4 round trips for almost every Workers invocation.

CColin but it seems like there's a lot of Neon fans in here who might've tried this ins...

M

Matt Silverlock•10/12/23, 10:40 AM

CColin but it seems like there's a lot of Neon fans in here who might've tried this ins...

M

Matt Silverlock•10/12/23, 10:41 AM

This isn’t Neon’s fault: their driver is great in lieu of other options in many serverless environments, but Hyperdrive exists because that’s still not good enough to get latency down.

MMatt Silverlock The Neon Serverless driver still needs to make 3-4 round trips for almost every ...

I

Isaac McFadyen•10/12/23, 8:40 PM

Question: how is this the case with Websockets? Is there still a handshake procedure that requires extra round-trips?

IIsaac McFadyen Question: how is this the case with Websockets? Is there still a handshake proce...

M

Matt Silverlock•10/12/23, 8:42 PM

TLS, then WebSocket. Every time.

MMatt Silverlock TLS, then WebSocket. Every time.

I

Isaac McFadyen•10/12/23, 8:42 PM

Do they not have edge nodes handling TLS closer to the Worker?

IIsaac McFadyen Do they not have edge nodes handling TLS closer to the Worker?

M

Matt Silverlock•10/12/23, 8:42 PM

No.

I

Isaac McFadyen•10/12/23, 8:42 PM

I know Prisma has many edge nodes despite having the DB be central.

I

Isaac McFadyen•10/12/23, 8:43 PM

Oh, interesting. OK then.

IIsaac McFadyen I know Prisma has many edge nodes despite having the DB be central.

H

Hello, I’m Allie!•10/13/23, 5:13 AM

Isn’t Prisma Edge CF already?

C

Colin•10/15/23, 11:23 PM

Hi! I'm getting a

Connection terminated unexpectedly

Connection terminated unexpectedly

error thrown while trying to query my Postgres DB w/ Hyperdrive. Using almost exactly the example code here:

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

client.connect()

client.connect()

is finishing fine, but

client.query()

client.query()

is throwing

Connection terminated unexpectedly

Connection terminated unexpectedly

. I'm setting

node_compat = true

node_compat = true

in my

wrangler.toml

wrangler.toml

as well. Any ideas?

C

Colin•10/16/23, 1:54 AM

^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. We had our certificate set to

rds-ca-rsa2048-g1

rds-ca-rsa2048-g1

, the issue fixed itself when changing back to the default

rds-ca-2019

rds-ca-2019

. Definitely a confusing error message (not sure if this is a

pg

pg

issue, or a Workers issue via the

connect

connect

call), but hopefully this can help someone else!

CColin ^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. W...

M

Matt Silverlock•10/16/23, 10:12 AM

This is because Hyperdrive doesn’t yet support custom CAs, and the “newer” AWS CA requires the client (Hyperdrive) to have it in its trust store.

CColin ^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. W...

M

Matt Silverlock•10/16/23, 2:02 PM

For clarity, after re-reading your message: this is via Hyperdrive, right? Not just

connect()

connect()

directly?

MMatt Silverlock This is because Hyperdrive doesn’t yet support custom CAs, and the “newer” AWS C...

C

Colin•10/16/23, 2:05 PM

I'm a little bit confused here. The docs do call out custom CA certs, but the default mode in

pg

pg

(not sure what Hyperdrive->AWS is using) doesn't verify certificates

MMatt Silverlock For clarity, after re-reading your message: this is via Hyperdrive, right? Not j...

C

Colin•10/16/23, 2:05 PM

Correct.

connect()

connect()

directly w/

sslmode=REQUIRE

sslmode=REQUIRE

doesn't verify the certs, so it works as expected

C

Colin•10/16/23, 2:05 PM

It's only when connecting via Hyperdrive, which I'm assuming is verify-ca or verify-full

CColin It's only when connecting via Hyperdrive, which I'm assuming is verify-ca or ver...

M

Matt Silverlock•10/16/23, 2:06 PM

No, per the docs: Hyperdrive does not support those modes. We only support

require

require

(and prefer, but we ultimately require TLS).

Similar Threads

Similar Threads

Similar Threads