SQLite VS MariaDB

If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.

https://github.com/sqlite/sqlite/tree/master/ext/lsm1

https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...

The sqlite code base is really well done. Lots of documentation.

https://github.com/sqlite/sqlite

Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...

Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c

That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.

Correct, see the github mirror[1]. I don't know how well supported that feature is compared to main branch. If it was completely stable, then it would have already landed in the main stable branch. Clarity about the roadmap of that branch would be nice.

1. https://github.com/sqlite/sqlite/tree/begin-concurrent

Including comprehensive comments, documentation and tests in a codebase takes time and effort.

Failing to do so creates code that is very difficult to maintain or for someone new to the codebase to understand.

However, time and effort may not be what the organization wants to pay for, and individuals may view their own incomprehensible code as something like job security, as they can't be replaced by someone else easily.

As an example of complicated code that's still well-documented, the open-source sqlite code is a good example, about 1/4 of the B-tree file is comments, every time a variable is defined there's a short note explaining what it's used for, every function has a comment header that's comprehensive, such that someone new to the codebase could construct a map of how it all works fairly quickly. It's a good model for how to avoid the problem:

https://github.com/sqlite/sqlite/blob/master/src/btree.c

MariaDB [1] is a community developed fork of MySQL, so you can feel free to use that in place of MySQL.

Another alternative would be Percona [2] which is a drop-in replacement for Oracle MySQL.

About PostgreSQL I haven't had that much of personal experience with it, but for sure I plan to learn it, because it has been battle-tested for years with lots of well-known projects, such as Django framework, for instance.

[1] https://github.com/MariaDB/server

[2] https://github.com/percona/percona-server

aka mariadb-dumpslow (aka mysqldumpslow) or pt-query-digest

My recollection is that it was created when Oracle took over MySQL in order to continue to have a community-driven GPLv2 "mysql compatible" server; I was expecting them to be more different than they are, but for comparison one is a "clean" GPLv2" and the other has more words and a link to oracle.com: https://github.com/mysql/mysql-server/blob/mysql-8.0.31/LICE... https://github.com/MariaDB/server/blob/mariadb-10.11.1/COPYI...

git clone --recursive --depth 1 --branch 10.5 https://github.com/MariaDB/server.git cmake . # needs cmake3 make make install

RUN git clone \ --branch mariadb-10.5.15 \ --depth 1 \ --recurse-submodules \ https://github.com/mariadb/server.git \ ~/server

Hi everyone! Our team just released EdgelessDB, an open-source database built on MariaDB that runs completely inside Intel SGX enclaves. As storage engine, it uses RocksDB with a custom encryption engine. The engine uses AES-GCM and is optimized for RocksDB’s specific SST file layout and the enclave environment. It has some nice properties like global confidentiality and verifiability and it considers strong attackers like malicious admins or rootkits. It also delivers rather low overheads (<10% for the TPC-C benchmark on Azure). In short: all data is only ever decrypted inside the enclave. This is different from other databases, where data and corresponding keys are processed in the clear in memory. We believe this is useful because (1) it’s very secure and (2) it enables some interesting use cases, like secure data pooling between parties. If you’re interested in trying it out: here’s a quickstart guide. In essence, you can run the Docker image with a single command on any recent Intel Xeon with SGX. Code and more info can be found on GitHub. Would be great to get your feedback on this :-)

MariaDB has 268 contributors vs 83 contributors to MySQL *