TLDR.Chat

Introducing ChronDB: A Git-Based Chronological Key/Value Database

GitHub - moclojer/chrondb: Chronological key/value Database storing based on database-shaped git (core) architecture 🔗

Chronological key/value Database storing based on database-shaped git (core) architecture - moclojer/chrondb

ChronDB is a chronological key/value database that utilizes a git-based architecture for data storage and indexing with Lucene. It features immutable and atomic data, ACID transactions, and a schemaless design, allowing users to query data at any historical point. With a RESTful server and Redis protocol support, ChronDB operates with various command-line options for customization. Users can configure it through an EDN file, manage data using git-like commands, and run tests or examples easily. The project is open for contributions and follows the MIT License.

What is ChronDB?

ChronDB is a chronological key/value database that uses a git-based architecture to store data and allows querying at any point in time.

How can I customize ChronDB's settings?

ChronDB settings can be customized using an EDN configuration file, where you can specify options like committer information, data storage directory, and logging preferences.

What are some of the commands I can use with ChronDB?

ChronDB supports various git-like commands such as diff, restore, branch, checkout, and more, enabling users to manage their data effectively.

Related