I am building a new immutable cryptographically verified database using IPLD data structures and prolly trees. This allows changes made anywhere to be transparently synced, and for operations to be commuted amongst untrusted peers, for instance allowing for shared index maintenance.

https://use-fireproof.com/docs/architecture

It's also the easiest way to write React apps. Here are some ChatGPT expert builders that I've trained to use the CSS framework of your choice with Fireproof: https://use-fireproof.com/docs/chatgpt-quick-start/#react-ex...

According to my estimation, a new database engine is born every week - mostly key-value and document databases. Only a small subset of them survive after one year. According to a guess by Stonebreaker, a DBMS takes around 7 years to become mature enough for general applications.

> According to my estimation, a new database engine is born every week

Fair. I'm talking about databases with funding backing them (either by universities or otherwise).

and DuckDB came out of academia too and is not based on Postgres either (highly relevant and notably absent in the authors list of academic DBs at the end of the article)

https://duckdb.org/pdf/SIGMOD2019-demo-duckdb.pdf

EDIT: oh the article is old

You may be interested in DuckDB's CIDR talk on the little miracles that made it possible. [0]

[0] https://twitter.com/motherduck/status/1615487300523429889

Dolt started in 2018: https://doltdb.com

Yes we have commit history from 2015 but that's from an earlier db project (noms) that we forked and built on top of

-- I started rqlite[1] in 2014[2], FWIW. While I didn't build the storage engine, or the consensus system, I've built the entire "management" part of the RDBMS from scratch. I'm almost 10 years at it, and there is still plenty to do.

[1] https://www.rqlite.io

[2] https://www.philipotoole.com/9-years-of-open-source-database...

Correct me if I’m wrong, but I don’t think RedPanda is a database. I see it as a streaming data solution, which the novelty factor can be discussed as well, since it’s basically Kafka.

KùzuDB[1] is an in-process graph database built from scratch and came out of academia too. We are from Data Systems Group at University of Waterloo, started since Sep 2020, and have a small team actively work on it now. 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

[2]: https://kuzudb.com/blog/meet-kuzu.html

[3]: https://kuzudb.com/blog/what-every-gdbms-should-do-and-visio...