OpenVibe.Events

OpenVibe.Events provides "durable events, subscriptions, delivery, retry, dead letters and replay for the network". Its README gives the status as alpha (roadmap Wave 3): it "runs and is tested; no service publishes to it in production yet". Its STATUS.json records it as not deployed. The README names events.openvibe.network as its domain and states that the domain keeps its placeholder page on OpenVibe.Sites until the plan's launch rule holds.

Purpose

The README calls it "the durable event backbone the network does not have yet". Authoritative services write domain changes and outbox events in one transaction, a relay publishes them to Events, consumers use inbox and idempotency receipts, and browsers receive authorized, resumable projections through a Realtime delivery plane. It is meant to replace the best-effort internal POSTs and webhooks between OpenVibe.Live, OpenVibe.Media, OpenVibe.Network and OpenVibe.Community. The first planned migrations are notifications, then Media ready/failed, then stream lifecycle.

What it owns

• the event, subscription, delivery, checkpoint and idempotency-receipt tables, in SQLite today;
• the canonical event envelope;
• priority classes, loop guards, backpressure, the dead-letter queue and replay;
• Realtime over Server-Sent Events, with cursor resume and gap detection; WebSocket and presence are not built yet.

Delivery is at least once and not strictly ordered. A failed delivery is retried up to 8 attempts and is then marked dead. The openvibe-events client library provides a transactional outbox for producers and an inbox for consumers.

What it does not own

Media bytes, game or media transport packets, and product business rules.

Dependencies

OpenVibe.Contracts and OpenVibe.Network; services call Events with Network client-credentials tokens. STATUS.json gives the runtime as Node 22, Express and better-sqlite3 on port 4300. The license is AGPL-3.0.