Vercel Service Markup

Re:Vercel Service Markup by bilalq on Wednesday May 03, 2023 @02:05AM (#35798597)

I'm interested in Neon and considering migrating to it. A few questions that I couldn't find a quick answer to:

1. When scaling to zero, what is the cold start for a request (including the time needed to make the connection)? Do you have benchmarks on this you could share?

2. Does Neon run a pgbouncer service or are customers expected to run their own? Is it better for AWS lambda functions to leave a connection open for the duration of the container lifecycle or open/close on each request?

3. Does Neon support HTTP for doing queries like serverless Aurora v1 does with its Data API? The use-case I have is direct AppSync GraphQL resolvers, not V8 isolate runtimes.

[ Parent | on HN ]

Re:Vercel Service Markup by nikita on Wednesday May 03, 2023 @02:40AM (#35798861)

1. Right now cold start is 3-5 sec. We are actively working on bringing it down. This is our users #1 complaint

2. Yes to pg bouncer. You have two connection strings with and without it

3. Yes. Check out our serverless driver.

[ Parent | on HN ]

Re:Vercel Service Markup by bilalq on Wednesday May 03, 2023 @02:28PM (#35805909)

Thanks for answering!

I saw your serverless driver, but it looks like it uses WSS, not HTTP. Is that correct, or is there an HTTP variant as well?

[ Parent | on HN ]