{"full_name":"barddoo/zedis","owner":"barddoo","name":"zedis","shard":"1","url":"https://github.com/barddoo/zedis","description":"Opinionated Redis in Zig","homepage":"","topics":["cache","redis","zig","caching","in-memory"],"tag_pages":["cache","caching","in-memory","redis","zig"],"language":"Zig","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/45905884?u=b67ae28938cb5ccf42db81a799e9a70b75b443c2&v=4","created_at":"2025-08-21T12:37:17Z","pushed_at":"2026-11-10T21:55:24Z","metrics":{"stars":298,"forks":14,"watchers":3,"issues":24,"prs":28,"releases":13,"issues_open":7,"issues_closed":17,"prs_open":2,"prs_closed":0,"prs_merged":26,"discussions":1},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-11"}},"history":{"dates":["2026-11-11"],"stars":[298],"forks":[14],"watchers":[3],"issues_open":[7],"prs_open":[2]},"boards":{},"same_owner":[],"issues":[{"number":40,"title":"Windows build currently failing","comments":3,"created_at":"2026-01-28T03:38:24Z"},{"number":3,"title":"Roadmap","comments":2,"created_at":"2025-09-24T16:04:50Z"},{"number":18,"title":"Add timeseries operations","comments":1,"created_at":"2025-10-08T14:14:31Z"},{"number":21,"title":"Add Streams support","comments":0,"created_at":"2025-10-08T14:16:30Z"},{"number":20,"title":"add geospatial support","comments":0,"created_at":"2025-10-08T14:16:12Z"},{"number":19,"title":"Add JSON support","comments":0,"created_at":"2025-10-08T14:14:55Z"},{"number":16,"title":"Add support for sets","comments":0,"created_at":"2025-10-08T14:11:56Z"}],"discussions":[{"number":29,"title":"Welcome to zedis Discussions!","comments":0,"category":"Announcements","created_at":"2025-10-22T13:40:01Z"}],"latest_release":{"name":"v0.2.2","tag":"v0.2.2","published_at":"2026-11-10T16:29:38Z","body":"\n### Added\n\n- AOF rewrite on a background thread: `BGREWRITEAOF` and automatic rewrites (`auto-aof-rewrite-percentage`, `auto-aof-rewrite-min-size`) replace the AOF with a snapshot of the live dataset, so it no longer grows without bound, and the server keeps serving while it runs. The store has no locks, so the rewrite thread never touches it: it replays the existing AOF into a private store (what a restart would load), writes strings (with TTLs), lists and time series as commands to a temp file, copies the log written meanwhile, and the writer thread splices on the last bytes, fsyncs, and atomically renames it into place. On 400k keys it took about 0.5 s with `PING` latency unchanged. It needs memory for a second copy of the dataset while it runs, outside `maxmemory`; because evictions are not logged to the AOF, that copy can also hold keys the live store has evicted (as a restart would). It is refused, leaving the AOF untouched, while the dataset holds bloom filters or search indexes, which commands cannot recreate. `INFO` reports `aof_rewrite_in_progress`, `aof_rewrites`, `aof_last_rewrite_time` and `aof_last_bgrewrite_status`; `METRICS` reports `zedis_aof_rewrites_total`.\n\n- Real observability: `INFO` now reports live command, connection, keyspace\n  hit/miss, expiry, eviction, network, memory, CPU, and AOF counters; new\n  `INFO commandstats`; `SLOWLOG GET|LEN|RESET`; `LATENCY LATEST|HISTORY|RESET|DOCTOR`;\n  and `METRICS` for Prometheus text scraping.\n- `slowlog-log-slower-than`, `slowlog-max-len`, `latency-monitor-threshold`,\n  and `command-timeout-ms` config keys, all mutable with `CONFIG SET`.\n- Graceful shutdown on `SIGINT`/`SIGTERM` and `SHUTDOWN [NOSAVE|SAVE]`. The\n  accept loops stop, clients are woken, and the AOF writer drains and fsyncs\n  before the process exits.\n- `CONFIG REWRITE` persists mutable directives to the config file using an\n  atomic temp-file rename, preserving comments and unrelated lines.\n- Read-only `O(N)` commands (`KEYS`, `SCAN`, `LRANGE`) accept a cooperative\n  deadline and reply `-TIMEOUT` instead of stalling without bound. `SCAN`\n  remains the `KEYS` replacement; the timeout bounds a stall rather than\n  removing it.\n- TLS listener via OpenSSL: `tls-port`, `tls-cert-file`, `tls-key-file`, `tls-ca-cert-file`, `tls-auth-clients` (`yes`/`no`/`optional`) and `tls-protocols`. TLS can run alongside plaintext or replace it with `port 0`; mutual TLS verifies client certificates against the configured CA. OpenSSL is linked statically by default.\n- RESP3 support, negotiated per connection with `HELLO [2|3] [AUTH default <password>] [SETNAME name]`. Connections stay on RESP2 until a client sends `HELLO 3`. Under RESP3, missing values reply with the null type (`_`), floats with the double type (`,`), and `CONFIG GET` and `BF.INFO` with a map (`%`). Pub/sub deliveries and `SUBSCRIBE`/`UNSUBSCRIBE` replies are push messages (`>`), while RESP2 subscribers on the same channel keep receiving arrays.\n\n### Changed\n\n- Startup no longer carries on after a failed AOF load. A damaged or unreplayable AOF now stops the server with an error instead of serving a partial dataset and appending to the bad file. `aof-load-truncated` (default `yes`) lets it cut off a final command left half-written by a crash, and `aof-load-broken` with `aof-load-broken-max-size` lets it discard a small corrupt tail; the cut is applied to the file so later writes append to a valid log. Any other corruption, or a command this build does not know, still stops startup.\n- The AOF is now loaded before its writer opens, since the writer begins appending at the file's length.\n\n### Fixed\n\n- A float reply longer than 32 characters (for example a time-series sample of `1e300`) overflowed a fixed buffer: a panic in safe builds, truncated output in `ReleaseFast`.\n\n---\n\n## Install\n\n**Linux (x86_64)**\n```bash\ncurl -Lo zedis https://github.com/charlesfonseca/zedis/releases/download/v0.2.2/zedis-v0.2.2-linux-x86_64\nchmod +x zedis && sudo mv zedis /usr/loca"},"readme":true,"readme_zh":false,"news":[],"stale":true,"snapshot_at":"2026-11-11T15:31:17Z","history_start":"2026-09-06"}