kuzu VS peloton

These two posts[2,3] explain where we are from and where we're going, if anyone is interested.

[1]: https://github.com/kuzudb/kuzu

Hi u/kyleireddit, I want to encourage you to try out KuzuDB: https://github.com/kuzudb/kuzu, which we are actively developing. One of our goals is to help educate developers more on where graph dbmss can offer value, so if you join our Slack channel and ask questions about graph dbmss and my students and I can answer some of your questions.

Then you can try Kùzu: https://github.com/kuzudb/kuzu. It should do quite well. We are new but actively developing the system and would love to help you when you are prototyping your application.

Not sqlite, but kuzu ( https://github.com/kuzudb/kuzu ) is an interesting project in this space. Fairly new, but already quite impressive IMHO.

I already mentioned Kùzu folks. They are doing an outstanding job of explaining what they do. Just follow their web 😀 They presented KùzuDB paper which brings interesting concepts to the graph query executions called factorization, S-Join and ASP-Join.

Proud to see my name (https://twitter.com/YingjunWu) mentioned in Andy's blog. I was Andy's visiting PhD at CMU and was the top 1 contributor to Peloton (https://github.com/cmu-db/peloton).

Today, building a database from scratch is extremely difficult, for several reasons:

I was one of the main authors of a research project called Peloton (https://github.com/cmu-db/peloton) which was later rebranded to NoisePage (https://github.com/cmu-db/noisepage). The initial version of RisingWave actually borrowed a lot from Peloton (fun fact: that's also how DuckDB https://duckdb.org/ started!), but we decided to rewrite in Rust due to development cost and security (e.g., memory leakage) considerations (more info: https://www.risingwave-labs.com/blog/building-a-cloud-database-from-scratch-why-we-moved-from-cpp-to-rust/).

I'll give you an example from my own industry. At my company we talk to university researchers, and one of the more famous university database researcher came to us to learn about our performance testing, because it turned out that the database they were working on for several years as a research project was completely unusable as they just forgot to think about that aspect. They had to abandon the project because there was no single feature that contributed to the performance issues and fixing the system was harder than starting from scratch. Here's the last commit if you don't believe me.