zheap VS dbdb.io

Hoping something like the zheap storage engine initiative should help us get past these bottlenecks in the future. Until then we may not be able to prevent the bloat but could certainly minimize the impact.

Hey, OP here -- it is a bit odd and also possibly immature to be so harsh on MySQL apropos of nothing. That said, I intended more to be pro-Postgres rather than anti-MySQL (it's a great piece of software, other DBs and Postgres learn from it all the time, zheap[0] exists to replicate what they've built, for example).

I also have to admit that I definitely want postgres every time I see MySQL. Maybe I need to read more on just how easy and amazing MySQL can be. Links welcome!

[0]: https://cybertec-postgresql.github.io/zheap/

Postgres's dominance is well deserved, of course. My only concerns with it, both are actively worked on, are bloat management (significant for update heavy workloads and programmers used to the MySQL model of rollback segments) and the scaling of concurrency (going over 500 connections). Bloat was taken over by Cybertec[1] after stalling for a bit and is funded (yay), while concurrency was also enhanced out of Microsoft [2]. All in all, an excellent future for our beloved Postgres.

[1] https://github.com/cybertec-postgresql/zheap

Have a look at https://dbdb.io/ for potential inspiration

Enter dbdb.io, the Database of Databases created and maintained by Carnegie Mellon Database Group. The catalog has entries of 841 databases (at the time of writing this article). It is fascinating to see the number of databases that have existed, the history about them and their technical details.

We automatically source the full list of open-source databases from https://dbdb.io/ and calculate daily updated metrics based on Github data. Check the full list of open-source databases on our website https://runacap.com/data/db-index/. All of them was included in analysis.

In dbdb.io there is no mentions of any github repos (https://dbdb.io/db/sqlite).