On the surface, they sound similar except that MySQL instances back Vitess and PostgreSQL instances back Citus. Though I could very well be missing some fundamental differences.
Vitess is a software suite that runs outside of MySQL while Citus runs within Postgres as an extension, so Vitess as more moving parts, but it also is better at handling more connections which has been a continual problem with PG in general.
Vitess supports more complicated sharding management (and requires more configuration) while Citus is simpler and lets you use all the flexibility of Postgres. Vitess has a more streamlined installation process (especially with Kubernetes) while Citus leaves it up to you to install the Postgres nodes.
Also note TiDB for a natively scalable MySQL-compatible database and CockroachDB for Postgres-compatible version.
I think the biggest difference other then the protocol is the tiered nature of vitess. Vitess has a different process that serves as the gateway and router while I believe Citis uses a plug-in inside postgres, and uses postgres to handle the connections.
Not knowing more about how Citus does it's sharding indexing I am sure there are differences there but I don't think I could explain them. Vitess has a very flexible and extendable sharding index that gives a lot of control over data locality to the user.
Oh, this is exciting! Really happy to see them get some traction. Well deserved and a awesome team. :)
Shameless plug: I designed, implemented and deployed their homepage (it seems they have iterated on it a bit), but was one of my first explorations using Gatsby combined with Netlify and Netlify CMS. It’s such a fun stack to work with and once handing it over, you feel a tad proud knowing it isn’t yet another Wordpress site.
I recommend it to anyone working with similar projects.
I can’t believe ordering by upload date in search doesn’t work. This hasn’t been working properly for at least a year or two. I don’t know before, but this is crazy
Is their "brilliant relational data storage system" the reason that YouTube can never show me the same list of my own videos I've uploaded to my account? One device shows one list, another shows another list (with some overlap), and going into different views of channel editing cause the lists to turn into yet another list. Maddening, and it's been doing it for years.
The simple fact that you can't search in search results or even search through lists... I'm not asking for a million options, I just want to be able to find a video I remember the title of without having to go through a bunch of garbage.
On the surface, they sound similar except that MySQL instances back Vitess and PostgreSQL instances back Citus. Though I could very well be missing some fundamental differences.
Vitess supports more complicated sharding management (and requires more configuration) while Citus is simpler and lets you use all the flexibility of Postgres. Vitess has a more streamlined installation process (especially with Kubernetes) while Citus leaves it up to you to install the Postgres nodes.
Also note TiDB for a natively scalable MySQL-compatible database and CockroachDB for Postgres-compatible version.
Not knowing more about how Citus does it's sharding indexing I am sure there are differences there but I don't think I could explain them. Vitess has a very flexible and extendable sharding index that gives a lot of control over data locality to the user.
Shameless plug: I designed, implemented and deployed their homepage (it seems they have iterated on it a bit), but was one of my first explorations using Gatsby combined with Netlify and Netlify CMS. It’s such a fun stack to work with and once handing it over, you feel a tad proud knowing it isn’t yet another Wordpress site.
I recommend it to anyone working with similar projects.