Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Edge-compatible Serverless Driver for Postgres

neon.tech

Post reply on HN
Print view View original

1–10 of 46 posts

Re: Edge-compatible Serverless Driver for Postgres

#3

Post by pbiggar »

nikita wrote: post #2

I’m Neon CEO. Happy to answer questions. We also have an interesting roadmap for the driver where we hope to keep driving latency and number of round trips down

Does Neon scale down storage? I'm paying GCP a lot for storage I don't use, and it's incredibly frustrating - they scaled me up no problem but won't let me scale down.

Re: Edge-compatible Serverless Driver for Postgres

#4

Post by bilalq »

nikita wrote: post #2

I’m Neon CEO. Happy to answer questions. We also have an interesting roadmap for the driver where we hope to keep driving latency and number of round trips down

I don't see pricing listed anywhere. Can you expand on what that might look like? Also, can Neon scale down to zero like serverless aurora v1, or is there a minimum capacity unit?

Re: Edge-compatible Serverless Driver for Postgres

#5

Post by Sujan »

The "How it works" section surprised me - I did not expect to see Websockets there.

Other serverless drivers or database APIs (PlanetScale Serverless Driver, AWS RDS Proxy or Prisma Data Proxy) usually use HTTP to replace the stateful TCP connection. The post explains a bit why this might be beneficial (can use existing tools, and use connection state) - but what about the other benefits and use cases of going with HTTP?

For example in that architecture the connection pool also moves from the application to the component in between and all that complexity can completely be removed from the app. Especially on serverless platforms, where in theory each request gets its own application with its own pool, that is huge. How does that work here? Or does the pool also move to the "WebSocket-to-TCP proxy" and you just did not highlight it in the post? (The graphic shows a "Connection Pool" but I can not really make sense of what that means.)

Re: Edge-compatible Serverless Driver for Postgres

#6

Post by nikita »

bilalq wrote: post #4
nikita wrote: post #2

I’m Neon CEO. Happy to answer questions. We also have an interesting roadmap for the driver where we hope to keep driving latency and number of round trips down

I don't see pricing listed anywhere. Can you expand on what that might look like? Also, can Neon scale down to zero like serverless aurora v1, or is there a minimum capacity unit?

Pricing is coming very soon. Dotting the is and crossing the ts

Re: Edge-compatible Serverless Driver for Postgres

#7

Post by nikita »

nikita wrote: post #6
bilalq wrote: post #4

Earlier quoted context omitted.

I don't see pricing listed anywhere. Can you expand on what that might look like? Also, can Neon scale down to zero like serverless aurora v1, or is there a minimum capacity unit?

Pricing is coming very soon. Dotting the is and crossing the ts

And yes. Scales to 0

Re: Edge-compatible Serverless Driver for Postgres

#8

Post by nikita »

pbiggar wrote: post #3
nikita wrote: post #2

I’m Neon CEO. Happy to answer questions. We also have an interesting roadmap for the driver where we hope to keep driving latency and number of round trips down

Does Neon scale down storage? I'm paying GCP a lot for storage I don't use, and it's incredibly frustrating - they scaled me up no problem but won't let me scale down.

Storage is multi tenant and bottomless. Unused storage spills to S3 and is cheaper. We pass savings to our users

Re: Edge-compatible Serverless Driver for Postgres

#9

Post by sakras »

nikita wrote: post #2

I’m Neon CEO. Happy to answer questions. We also have an interesting roadmap for the driver where we hope to keep driving latency and number of round trips down

I’m curious why not implement websockets into Postgres natively instead of relying on a proxy server? Wouldn’t that be the way to minimize latency?
Post reply on HN