rheo 0.6.0
“Durable consumer-group semantics over searchable databases (MongoDB, PostgreSQL/SQLite via Ecto, ETS). Partitions, contiguous ACK frontier,…”
Near-zero recent downloads for registry packageRelease published within seven days
SHA-256a3ad128db890f045d6eac8092d44968c56619943531d1cbed881a3cb08bac84d
MaleculeH₂(Cm₂Os)Md(Pa)
Evidence
5:28… Consumption records progress, leases, retries, and
6 dead-letters in separate consumer-group state. Delivery is **at-least-once**:
7 after a crash …
13:10… ons.
14
15 From **v0.6**, `Rheo.Backend.Ecto` runs the same API on a **host-owned**
16 `Ecto.Repo` (PostgreSQL or SQLite). Mongo remains `Rheo.Backend. …
51:24… .lag("market-events", "risk")
52
53 Search history with `query` / `query_page` / `stream_query`. Replay without
54 copying events via `create_group` sta …
55:15… /3` (`confirm: true`). See `Rheo.Event.Lineage` for correlation
56 metadata and `Rheo.Partition` for routing helpers.
57
58 See also `Rheo.Consumer` fo …
106:54… ult_backend_handle(rheo, backend_mod)
107 backend_opts = Keyword.put(backend_opts, :name, handle)
108
109 children = [
110 {Registry, keys: :unique, name: Rheo.Names.registry(rheo)},
111 backend_m …
No evidence locations were recorded for this file. Raw result