LumoSQL

Summary

LumoSQL LumoSQL is a modification (not a fork) of the SQLite embedded data storage library, which is among the most-deployed software. We are currently in Phase II of the project. If you are reading this on GitHub you are looking at a read-only mirror. The master is always available at lumosql.org. LumoSQL adds security, privacy, performance and measurement features to SQLite. Benchmarking SQLite can test and compare results consistently across many kinds of system and configurations using the Not-forking tool. Example: Pluggable backends LumoSQL can swap back end key-value store engines in and out of SQLite. LMDB is the most famous (but not the only) example of an alternative key-value store, and LumoSQL can combine dozes of versions of LMDB and SQLite source code like this: In LumoSQL 0.4 there are three LumoSQL backends: We are looking at some interesting new development in key-value storage to add and benchmark. Encryption and corruption detection, optionally per-row LumoSQL adds modern encryption to SQLite, including Attribute-Based Encryption (ABE). This can be done on a per-row basis, and also includes per-row checksums so that any error can be noticed quickly and located down to the individual row. Per-row checksums also make some search and comparison operations much faster. Organised and Supported LumoSQL is distributed under very liberal MIT licence terms. LumoSQL is supported by the NLNet Foundation. LumoSQL runs on x86, ARM-32 and RISC-V architectures, and many Linux and BSD OSs. Table of Contents Design, Not-Forking and Participating If you are reading this on Github, then you are looking at a mirror. LumoSQL is is maintained using the Fossil repository. If you want to participate in LumoSQL there is a forum, and if you have code contributions you can ask for access to the respository. LumoSQL has multiple upstreams, but does not fork any of them despite needing modifications. The novel Not-forking tool semi-automatically tracks upstream changes and is...