declarative relay deployment on hetzner
relay-eval.waow.tech
atproto
relay
docs: credit lightrail for zlay collection index design
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+1
-1
+1
-1
docs/architecture.md
+1
-1
docs/architecture.md
···
70
70
71
71
**same model, different internals.** zlay crawls PDS hosts directly — it is not a fan-out relay. `RELAY_UPSTREAM` (default: `bsky.network`) is a bootstrap seed used once at startup to populate the host list via `listHosts`. after that, all data flows directly from each PDS.
72
72
73
-
**inline collection index.** instead of running collectiondir as a sidecar, zlay indexes `(DID, collection)` pairs directly in its event processing pipeline. storage is [RocksDB](https://rocksdb.org/) with two column families (`rbc` for collection→DID lookups, `cbr` for DID→collection cleanup). serves `listReposByCollection` from the relay's HTTP port — no separate service.
73
+
**inline collection index.** instead of running collectiondir as a sidecar, zlay indexes `(DID, collection)` pairs directly in its event processing pipeline, inspired by [fig](https://tangled.org/microcosm.blue)'s [lightrail](https://tangled.org/microcosm.blue/lightrail). storage is [RocksDB](https://rocksdb.org/) with two column families (`rbc` for collection→DID lookups, `cbr` for DID→collection cleanup). serves `listReposByCollection` from the relay's HTTP port — no separate service.
74
74
75
75
**optimistic validation.** on a signing key cache miss, zlay passes the frame through immediately and queues the DID for background resolution. first commit from an unknown account is unvalidated; subsequent commits are verified. indigo blocks until resolution completes.
76
76