build · oxidb v0.25.21 8 entries on disk
The /dev/oxide

A build log on shipping OxiDB — notes, post-mortems, and the occasional flame war about JSON parsing, pressed straight onto an embedded engine running inside this process.

archive · sorted desc by ts build log

20 entries on disk · page 2/3. Each post + every image lives inside one embedded OxiDB data dir — no external store, no migrations, no schema files.

  1. 0009 · 2026-05-04

    running OxiDB inside this gunicorn worker

    @admin 301 words oxidb-embedded

    This whole blog is one process. Gunicorn worker, eight threads, Django on top, OxiDB linked in as a shared library and called via ctypes. There is no oxidb-server running next to it. There is …

    hero image for: running OxiDB inside this gunicorn worker
  2. 0010 · 2026-05-03

    why JSONB and not JSON text

    @admin 257 words oxidb-embedded

    OxiDB stores documents as JSONB — Postgres-style binary JSON — not as JSON text. That choice pays off in exactly one place and it pays a *lot*: partial extraction. JSONB has a header section …

    hero image for: why JSONB and not JSON text
  3. 0011 · 2026-05-02

    OxiMem — a Redis wire on the same engine

    @admin 189 words oxidb-embedded

    OxiMem speaks the Redis RESP protocol on a separate port (`OXIDB_OXIMEM_PORT`) and shares process memory with the document engine. `redis-cli`, `node-redis`, `go-redis`, every Redis client just works. No translation shim. What's implemented: strings (GET/SET/INCR/EXPIRE), …

    hero image for: OxiMem — a Redis wire on the same engine
  4. 0012 · 2026-05-01

    aggregation pipeline — $match, $group, $sort, $dateHistogram, $percentile

    @admin 194 words oxidb-embedded

    The aggregation surface is MongoDB-style — same operator names, same input/output shape, same `db.aggregate(coll, [stages...])` API. Stages execute as an iterator chain so intermediate results never need to fit in memory. Stages implemented today: …

    hero image for: aggregation pipeline — $match, $group, $sort, $dateHistogram, $percentile
  5. 0013 · 2026-04-30

    REST + JWT + per-document security rules (Firebase, but smaller)

    @admin 205 words oxidb-embedded

    Set `OXIDB_HTTP_PORT` and OxiDB exposes a REST surface for CRUD, SQL, aggregation, procedures, and blob ops. JSON in, JSON out, CORS, 64-thread pool. The whole Firebase experience without the Google account. **JWT auth.** `OXIDB_JWT_SECRET` …

    hero image for: REST + JWT + per-document security rules (Firebase, but smaller)
  6. 0014 · 2026-04-29

    change streams — onSnapshot without polling

    @admin 222 words oxidb-embedded

    Every successful write — insert, update, delete, `commit_tx` — emits a `ChangeEvent` to a process-wide broker. Subscribers receive a stream of events filtered by collection, document id, or a small predicate. No polling, no …

    hero image for: change streams — onSnapshot without polling
  7. 0015 · 2026-04-28

    GELF log ingestion — auto-index, retention, alerts

    @admin 205 words oxidb-embedded

    OxiDB doubles as a log destination. Set `OXIDB_GELF_PORT=12201` and it speaks GELF UDP. Graylog clients, Docker's `gelf` log driver, fluent-bit's gelf plugin — all just point and stream. Auto-decompresses chunked + gzipped GELF. **Auto-indexing.** …

    hero image for: GELF log ingestion — auto-index, retention, alerts
  8. 0016 · 2026-04-27

    encryption at rest — AES-256-GCM in the storage layer

    @admin 223 words oxidb-embedded

    Pass an `EncryptionKey` to `OxiDb::open_with_options` (or the env var `OXIDB_ENCRYPTION_KEY=/path/to/keyfile`) and every byte that leaves the in-memory representation is encrypted before it hits the disk. AES-256-GCM, per-write random 96-bit nonce, authenticated, no chained mode …

    hero image for: encryption at rest — AES-256-GCM in the storage layer