vitess VS Scylla

With Vitess likely merging a lot of its binaries into a single unified binary: https://github.com/vitessio/vitess/issues/7471#issuecomment-...

... it would be a wild future if Vitess replaced the underlying MySQL engine with this as long as the performance is good enough.

Thank you for the compliment!

We recently started adding support for CTEs in Vitess! You can check out https://github.com/vitessio/vitess/pull/14321 if you want to see some technical details of the implementation.

For now, we have added preliminary support by converting them to derived tables internally, but we believe that we need to make CTEs first-class citizens themselves of query planning. Once we make that change, we can look towards supporting recursive CTEs.

This however will take some time, but then, all good things do!

Why would it be a Google project? https://github.com/vitessio/vitess

This is great news. I strolled around https://github.com/vitessio/vitess/issues/12967.

Are there any public discussions of more trade-offs vitess has to make to enable fks?

MySQL + Vitess I noticed Slack gets by using MySQL because they're using Vites. From Slack's post (https://slack.engineering/scaling-datastores-at-slack-with-vitess/) it seems like they choose Vites because it facilitated a smooth transition because it's built on top of MySQL.

This sounds very similar to the connection pooling done by vitess https://vitess.io/.

https://github.com/vitessio/vitess/issues/12967

A lot of this is possible thanks to the magic of Vitess.

"Vitess is a database clustering system for horizontal scaling of MySQL."

https://github.com/vitessio/vitess

Then I decided to talk to my boss and ask him if I could work with the YARG guys and the condition was to create something cool enough to implement ScyllaDB (NoSQL Wide-column Database) since I'm working as a Developer Advocate there. You won't believe how the simplicity and scalability brought by ScyllaDB perfectly fit the needs of YARG.in!

ScyllaDB now has initial support for a new replication algorithm: tablets...

Scylla which is a C++ implementation of the Cassandra distributed K:V store https://github.com/scylladb/scylladb

What you say is impossible, we pretty successfully apply at ScyllaDB (see https://github.com/scylladb/scylladb/commits/master).

I'm not sure 100% of the commits compile & pass all tests - there may be some mistakes - but generally we're in a pretty good state, and the clean git log is being successfully used for bisecting.

If you want even larger scale - if I understand correctly, the Linux kernel practices a similar thing, which is where we got this practice from (ScyllaDB founders came from kernel development). And since Git was originally created to help developing Linux - that's where you want to look for good practices.

Examples: - Vitess - MySQL cluster - YugabyteDB - ScyllaDB - Couchbase - ArangoDB