The PlanetScale serverless driver for JavaScript

Post by joshstrange » Thu, Aug 18, 2022, 7:48 PM UTC

mattrobenolt wrote: post #28

joshstrange wrote: post #25

Earlier quoted context omitted.

> This specifically is targeting environments where a MySQL client isn't able to run. Oh, absolutely and I didn't mean to imply it wasn't useful, I was just saying I went down the Prisma path and will be sticking with that. Even so I'm glad this exists for times that I don't need the full weight/power of Prisma but do want to talk to a PlanetScale DB.

I went down the Prisma path investigating JavaScript ORMs, and... I have opinions. :) I feel that what we have would be useful within a Prisma context, but given their complexity and how Prisma works, it's likely not very practical with their "engine".

Post by brundolf » Thu, Aug 18, 2022, 8:18 PM UTC

mattrobenolt wrote: post #13

mattrobenolt wrote: post #9

Earlier quoted context omitted.

Great question! Author of a lot of the infrastructure surrounding this here. I plan on following up with a more technical deep dive on some of these aspects, but it's quite a bit hard to do a 1:1 comparison. While, obviously, HTTP also uses TCP, I'm going to assume you're asking more about the binary MySQL protocol vs HTTP. On the surface, yes, HTTP is going to have more overhead with headers and the other aspects th…

There are, in my opinion, a few other concrete benefits outside of performance too that I didn't touch on. I plan on touching on them more in my follow up blog post though. A lot of this for me/us at this point is still theoretical since we don't have tons of application yet. Serverless was an easy first target since they require HTTP as the transport. The real experiments will come when we say, put together a Python…

Post by mattrobenolt » Thu, Aug 18, 2022, 8:33 PM UTC

joshstrange wrote: post #31

mattrobenolt wrote: post #28

Earlier quoted context omitted.

I went down the Prisma path investigating JavaScript ORMs, and... I have opinions. :) I feel that what we have would be useful within a Prisma context, but given their complexity and how Prisma works, it's likely not very practical with their "engine".

That’s fair. They are the only game in town, last I checked, that has full (good) TypeScript support which is a must-have for me. TypeORM is the other I know about and I’ve used it as well but I greatly prefer Prisma. Other than having to bundle the engine I’ve been very happy with Prisma + PlanetScale. I’m open to any other TypeScript ORMs if you know of them.

Post by tbarn » Thu, Aug 18, 2022, 10:38 PM UTC

gsanderson wrote: post #26

joshstrange wrote: post #14

Earlier quoted context omitted.

I mean I'm using PlanetScale with Prisma ORM on AWS Lambda right now without issue. Unlike many DB providers, PlanetScale supports nearly unlimited connections. I think I saw in their docs they have a soft-limit of something like 250K connections. I used Aurora Data API before moving off Aurora Serverless (insane pricing) to Prisma and PlanetScale, I don't think I'd go back to the HTTP API as Prisma works very well a…

I agree about Aurora Serverless pricing! Yeah, I think this new thing would be less useful for Lambda as that does support TCP connections. However a HTTP API is required for e.g Cloudflare Workers where you can't create a normal MySQL client. I think that's where this could shine.

Post by asadawadia » Fri, Aug 19, 2022, 12:30 AM UTC

alexcroox wrote: post #2

This is huge for me. I went down the path of trying to build an entire API on CF Workers and the biggest stumbling block was no easy access to external relational databases due to a lack of v8 compatible connectors. This was before the D1 announcement of course.