An ultra high-performance lightweight embedded and server OLTP relational database management system written in C.
CrossDB is an ultra high-performance lightweight relational database management system designed for both embedded and server OLTP (Online Transaction Processing) workloads. It provides ACID compliance, SQL support with MySQL extensions, and multiple storage models including in-memory and on-disk options. The project aims to deliver exceptional performance while maintaining a small footprint suitable for resource-constrained environments.
Developers and engineers building applications that require a high-performance, lightweight database for embedded systems, edge computing, or server applications where SQLite or similar embedded databases are insufficient. System architects needing flexible deployment options from embedded to standalone server modes.
CrossDB offers significantly higher performance than SQLite while maintaining a lightweight architecture, with additional enterprise features like replication, MVCC concurrency control, and hybrid storage models. Its C implementation and cross-platform support make it ideal for performance-critical applications across diverse hardware environments.
Ultra High-performance Lightweight Embedded and Server OLTP RDBMS✨
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Shows significant speed advantages over SQLite and C++ STL containers in random access benchmarks, making it ideal for OLTP workloads.
Supports server-less, embedded server, and standalone server modes across Linux, Windows, macOS, and FreeBSD, enabling flexible use from embedded to server environments.
Allows per-table designation for in-memory, on-disk, or RamDisk storage, providing fine-grained control over performance and persistence strategies.
Implements SQL with extensions from MySQL and supports data types like JSON, INET, and MAC addresses, easing migration for users familiar with MySQL.
The README explicitly states the project is in early stages and lacks stability, with many features marked as TBD, making it risky for production use.
Key features like foreign keys, row-level locks, additional language bindings, and user management are not yet implemented, limiting its utility for complex applications.
Building on Windows requires installing MINGW64, CMake, and make, adding setup complexity compared to simpler, more established databases.