I'm curious, how does Vitess compare to Citus?
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.
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.