tbarn

Nice, someone just shared it with me yesterday!

I've been working with the team at Not Diamond and trying out the private beta for a couple of weeks, and the routing experience is great. It makes it really easy to use different models and also route based on different tradeoffs. All I had to do was grab API keys from the different LLM APIs and quickly set it up.

I totally agree. If anyone has tried to hire a technical product marketer who "gets it," they will understand there is a really small group of people who have the technical understanding and ability to communicate beyond "X is the best platform." Sometimes early stage companies think their engineers will be able to do it, but often it is not true. They need someone who both sees the internal AND external view of things.

Just wait until December, we will release more information about foreign key constraints on PlanetScale then!

It shouldn't be too many hoops, fairly standard foreign key constraint support. Let us (PlanetScale) know if it is!

The good news on the PlanetScale side is that foreign key constraint support is coming, so in the future this would no longer be an issue.

This number of connections on any of the paid plans should be no issue.

We are working on foreign key constraint support right now. :)

We are getting the chart updated with the pricing now. Thanks for pointing that out.

KubeCon talks should be out in the next month or so and it has more details.