[kelvich]

> The article ends with the statement that you are pretty much done here for now. Would optimizing your TLS termination not maybe offer some more ways to speed this up? Or is that also already fully optimized?

No, we don't do early termination yet, but it makes sense to try it out too. Here we mostly concentrated on how far we can get in terms of reducing number of round-trips.

> I did not realize before that your approach with Websockets actually meant that there was no application/client side pooling of connections. What made you choose this approach over an HTTP API (as for example PlanetScale did) anyway?

To keep compatibility with current code using postgres.js.

[janpio]

> To keep compatibility with current code using postgres.js.

That makes a lot of sense - not needing an additional driver/client package is indeed a good point. Any plans to add a HTTP based API though anyway?

[nikita]

Potentially. We will follow what our users will ask us to do.