3 ms·

"Won" is a statement which is accurate for the moment in which I did my review. I think all of these database providers are great. Postgres people need a solut

"Won" is a statement which is accurate for the moment in which I did my review. I think all of these database providers are great. 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.

throwusawayus 3y ago
youtube migrated away from vitess several years ago 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
- correct_beans 3y ago
  Nobody cares. Millions of apps run on mysql despite your objections. Good luck with that one
- sgammon 3y ago
  I'll believe it when I see it. Millions of applications use MySQL, and Vitess has only matured and grown. 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.
  - throwusawayus 3y ago
    think of big features added to oracles Mysql in past two years. Thats ten releases: eight most recent 8.0.xx, and 8.1 and 8.2. what are they? are you using any? does it really not worry you at all?
    - sgammon 3y ago
      I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
      - throwusawayus 3y ago
        ok. json columns were put in eight years ago
        sgammon 3y ago
        Great sounds to me like a fine pace
benatkin 3y ago
Not accurate IMO. It's marketing a feature for giant users like YouTube and GitHub as important for everyone. Neon and sqlite are winning from my perspective. The BlueSky move to thousands of sqlite databases should inspire similar architectures in other apps. Vercel has stopped gushing about PlanetScale in particular and now offers never options including Neon.
- correct_beans 3y ago
  ??? Bluesky isn't at all a typical application architecture. The code is gross and insanely complex for a regular app. Vercel still gushes all the time about Planetscale, and so does Cloudflare. Neon is the provider du jour for postgres
- sgammon 3y ago
  Well, you are welcome to do your own review and share the results. At the time we were deciding between all the major DB as a Service providers. Not everyone has the same architecture as Bluesky, and from reading the code it seems pretty mechanical and complex.
  - benatkin 3y ago
    I'm welcome to simply ignore PlanetScale unless I want to learn MySQL or need some performance characteristics that only make a difference in rare cases. Even if it is good enough I don't want to read the MySQL docs. If PlanetScale wants their product to be more welcoming, they'll have to distance it more from Oracle than it is.
    - sgammon 3y ago
      ? MySQL, in this case, is simply a protocol. Planetscale and Vitess are not affiliated with Oracle at all. I don't understand your point. Furthermore, we use Planetscale from an ORM. I don't think I have "read the MySQL docs" in years.

throwusawayus 3y ago

youtube migrated away from vitess several years ago 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

correct_beans 3y ago
Nobody cares. Millions of apps run on mysql despite your objections. Good luck with that one
sgammon 3y ago
I'll believe it when I see it. Millions of applications use MySQL, and Vitess has only matured and grown. 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.
- throwusawayus 3y ago
  think of big features added to oracles Mysql in past two years. Thats ten releases: eight most recent 8.0.xx, and 8.1 and 8.2. what are they? are you using any? does it really not worry you at all?
  - sgammon 3y ago
    I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
    - throwusawayus 3y ago
      ok. json columns were put in eight years ago
      - sgammon 3y ago
        Great sounds to me like a fine pace

benatkin 3y ago

Not accurate IMO. It's marketing a feature for giant users like YouTube and GitHub as important for everyone. Neon and sqlite are winning from my perspective. The BlueSky move to thousands of sqlite databases should inspire similar architectures in other apps. Vercel has stopped gushing about PlanetScale in particular and now offers never options including Neon.

correct_beans 3y ago
??? Bluesky isn't at all a typical application architecture. The code is gross and insanely complex for a regular app. Vercel still gushes all the time about Planetscale, and so does Cloudflare. Neon is the provider du jour for postgres
sgammon 3y ago
Well, you are welcome to do your own review and share the results. At the time we were deciding between all the major DB as a Service providers. Not everyone has the same architecture as Bluesky, and from reading the code it seems pretty mechanical and complex.
- benatkin 3y ago
  I'm welcome to simply ignore PlanetScale unless I want to learn MySQL or need some performance characteristics that only make a difference in rare cases. Even if it is good enough I don't want to read the MySQL docs. If PlanetScale wants their product to be more welcoming, they'll have to distance it more from Oracle than it is.
  - sgammon 3y ago
    ? MySQL, in this case, is simply a protocol. Planetscale and Vitess are not affiliated with Oracle at all. I don't understand your point. Furthermore, we use Planetscale from an ORM. I don't think I have "read the MySQL docs" in years.