unqlite
An Embedded NoSQL, Transactional Database Engine
What is unqlite?
An Embedded NoSQL, Transactional Database Engine
Overview of unqlite
What it is
UnQLite is an embedded NoSQL transactional database engine for C and C++ applications. It is self-contained, serverless, and runs in-process, storing data in a single portable file. The engine provides two layers: a raw key/value store for binary-safe records and a document store powered by the Jx9 embedded scripting language. The current public release is version 1.2.1.
Key features
- Embedded: no separate daemon, socket protocol, or service to deploy
- Transactional: ACID semantics for local storage workloads
- Simple distribution: a database is typically one file on disk
- Portable: the file format is cross-platform
- Flexible: use key/value APIs directly or use the document store and Jx9 layer
- Small integration surface: the recommended embed path is the amalgamation
- Optional threading support: enable at compile time with
UNQLITE_ENABLE_THREADS
Use cases
UnQLite is suitable for applications that need embedded local storage without a separate database server. It can be used for key/value storage, document-oriented scripting with Jx9, and scenarios requiring ACID transactions in a single-file database. It is designed for C and C++ programs that need a lightweight, portable database engine.
Getting started
The fastest way to embed UnQLite is to compile your application together with unqlite.c. Example compilation commands from the README:shcc -O2 -std=c99 -I. your_app.c unqlite.c -o your_app``````batcl /nologo /TC /I. your_app.c unqlite.cFor threading support, define UNQLITE_ENABLE_THREADS when building.
License and pricing
UnQLite is distributed under the 2-Clause BSD license. The license text is in the LICENSE file in the repository. The pricing type is open source.
Based on the project's public README and repository metadata.