Kronotop: Horizontally scalable, distributed, transactional document database
3 comments
Me: "I’m done trying every new database on HN."
Also me, 3 minutes later: git clone https://github.com/kronotop/kronotop
Damn it. You had me at "ACID + RESP3."
Looked at the repo. License of mix of Apache 2.0 and BSL is rather unclear.
Here is the additional use grant: You may make use of the Licensed Work, provided that you may not use the Licensed Work for a Database Service. A "Database Service" is a commercial offering that allows third parties (other than your direct employees and contractors) to access the functionality of the Licensed Work by creating or managing tables whose schemas are controlled or managed by such third parties.
Please visit the project page on GitHub: https://github.com/kronotop/kronotop
Kronotop is a distributed, transactional document database designed for horizontal scalability. It provides a robust foundation for applications needing to manage large volumes of documents while ensuring strong consistency guarantees for critical metadata operations. By leveraging FoundationDB as its transactional backend for metadata and indexes, Kronotop delivers ACID integrity, offering reliability often sought in demanding environments.
Kronotop features an MQL-like query language and uses the RESP3 wire protocol, ensuring broad compatibility with the Redis client ecosystem. It implements core Redis in-memoru data structures like Strings and Hashes, alongside its own specialized structures: ZMap (an ordered key-value store acting as a RESP proxy for FoundationDB) and Bucket (designed for storing JSON-like documents). While document bodies are stored directly on local filesystems, Kronotop uses BSON as the default data format to organize and store within Buckets, with JSON also available.
https://github.com/kronotop/kronotop