rajivharlalka

filedb: Store Key-Value Data in Append-Only Files

FileDB is a Zig key-value store inspired by Bitcask, using append-only disk files and an in-memory index for lookups. It also includes a Redis-compatible client, but its inactive status and single-contributor history make production adoption a decision that needs careful review.

View on GitHub Compare
Stars
198
Forks
7
Stars, last 30 days
+0
Last commit
1.3 years ago
Contributors
1

Our take

Inactiveno commits in over a year

Health score

16/100

How it is scored
Activity
19
Community
4
Issues
21
Pull requests
20

+0 stars in the last 30 days

  • Fewer contributors than 91% of the projects we track

FileDB is a useful Bitcask-inspired Zig project to explore, but its year-plus without commits, lack of releases, and reliance on one contributor make it a cautious choice for production.

Good fit if

  • You want to study or experiment with an append-only key-value store in Zig.
  • You can review the implementation and validate its behavior for your own workload.
  • You want to investigate its Redis-compatible client for basic commands.

Look elsewhere if

  • You need an actively maintained storage dependency with recent releases.
  • Your team needs visible maintenance shared across multiple contributors.
  • You require established test or CI coverage, which is not listed in the supplied project facts.
All health signals
Last commit2025-06-14 (1.3 years ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors1
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age16 months

Checked on 2026-10-09 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

198

Forks

7

Change since Nov 17, 2026: 0 stars·0 forks

Overview

FileDB is a disk-based key-value store written in Zig. It addresses a common storage tradeoff by appending records to disk while keeping metadata in memory, so the database can locate values without scanning the data files.

It is intended for developers interested in a Bitcask-style storage engine or a lightweight key-value store they can embed in a Zig application. A Redis-compatible client is also described in the README. The project has had no commits in over a year and its work is concentrated in one contributor, so treat it as an exploratory option rather than an actively maintained dependency.

Key Features

  • Appends records to an open data file rather than updating values in place.
  • Keeps record locations in an in-memory hash table for direct lookups.
  • Rotates data files and retains older files for reading.
  • Compacts data files into a combined file and updates the metadata index.
  • Supports periodic syncing, with an option to sync on each request.
  • Provides put, get, delete, and key-listing operations.
  • Offers hint-file creation and loading for the key directory.
  • Includes a Redis-compatible client with examples for basic PING, GET, and SET commands.

Use Cases

  • Zig developers evaluating Bitcask-style storage for a small application or prototype.
  • Engineers studying how append-only files, indexes, and compaction work together in a key-value store.
  • Teams that need a simple key-value API and are prepared to inspect and test the implementation themselves.
  • Redis-protocol clients or tools that need to experiment with the included Redis-compatible interface.

What you need

Detected in the repository

  • Zig (main language on GitHub)

Getting Started

Start with the FileDB README for the API and project details. The README does not provide an installation command or a concise build-and-run sequence.

License in Plain Words

No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.

Considerations

The repository is marked inactive, with no commits in over a year and no releases in the past year. The measured contributor history consists of one person, so maintenance depends heavily on that contributor. The supplied project facts also list no tests or CI configuration; validate persistence, recovery, compaction, and sync behavior before relying on it. No license is specified in the provided repository metadata, so confirm the repository's licensing terms before adopting or redistributing the code.

Found this useful?

Share it with someone who would like filedb.

Comparisons