Vitess 18
planetscale.com
planetscale.com
I wonder how practical it'd be to attempt using this now, or would I have to go through too many hoops or footguns?
It shouldn't be too many hoops, fairly standard foreign key constraint support. Let us (PlanetScale) know if it is!
That said, true FK support is a very nice addition. However it really pains me to you MySQL, as it has a baggage it carries and is not SQL compliant. Thats why i always go for Postgres instead.
https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql...
You telling me we can make a ReactJS for terminals? ha
Shared nothing architectures are useless for 99% of the market and break compatibility with the single node databases.
I’ve never had compatibility issues with single-node databases. It “just works” in the cloud and locally thanks to MySQL support in vitess.
Anyone can claim this and LVM together 20 64TiB EBS volumes and put them on one big node. That's not sharding or bottomless.
Sharding and a shared nothing have incredible benefits to anyone who has a requirement for uptime, scalability, and cost reduction. We’ve avoided supporting parts of MySQL that make scaling worse and are working to add them back in ways that work, like FKs. In return for not supporting all MySQL features we hand back an immense amount in return. This is something our customers have been happy with.
I believe Neon will be one of the providers that sticks around to do this. Comparison is the thief of joy.
There is a ton of work internally that will improve the uptime as we get to GA.
https://vercel.com/changelog/vercel-postgres-is-now-availabl...
I think PlanetScale is the most mature option on the market right now by far
I don't think _won_ is the right term. _In the lead_ would be a better phrase in my opinion. I think Planetscale being based on MySQL will hurt them in the long run. Tying themselves to Orcale is already hurting them, having to fork MySQL to add vector support for instance. Neon, on the other hand, gets to benefit from a larger and much more collaborative community in Postgres, as do other Postgres vendors like Supabase, Azure, AWS, Tembo, Nile, etc.
Please continue to use the vendor that you find works for you, however.
Postgres people need a solution just as much as MySQL people do. I think when it comes to Postgres, the name in my mind is Neon, even though I am a Planetscale customer. In my current job, I need MySQL, but to be clear I wouldn't be against Neon (even as a PS fan) if I had a direct need for it.
Neon has a reason to exist even if Planetscale is in the "lead." There is a huge community around Vitess, including, you know, YouTube, not to mention MySQL, which also has an enormous community.
Keep up the good work. Databases as a service are a good thing to be doing.
Mysql product is circling drain under oracles direction anymore. New 8.x “innovation” releases lack any important features. even Mariadb is out executing oracle despite being broke!
Mysql community is in bad shape too. Official slack channel is avalanche of lazy newbie questions. Official linkedin group is endless spew of “learn sql cheat sheet”
Sad. It’s done for. community may still be “enormous” but that is bad thing when its communication channels overrun by sub-bootcamp-level devs
They said Java was done like five times. It's in the midst of another massive revival. I think the bet on MySQL is a solid one, and I think reasonable minds should be able to differ about this, so I can't bring myself to be as sure as you seem to be.
I can say this: Our app, built on Planetscale and MySQL's protocol, has been fantastic to work with. We run locally against MySQL and H2, and in prod against Planetscale. Everything works really well. Boost, replication, backups, branching, etc etc. We use all of them. Every feature works great, does exactly what it says on the tin. We have never had a single problem.
So, in theory, yes, these things are all on a timeline of some kind between life and death, but I find it very hard to believe MySQL or Vitess are near the end of theirs.
what are they? are you using any? does it really not worry you at all?
Furthermore, we use Planetscale from an ORM. I don't think I have "read the MySQL docs" in years.
That is all that I am aware of in this subthread. FWIW, Nikita and Sam have their affiliations in their profiles.