peloton VS mutable

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.

There's also mutable that compiles to WASM and lets it get JITed by v8 https://github.com/mutable-org/mutable.