From signal
to flow.
GenesisDB Syncra turns your event sourcing streams into unified business flows. Connect multiple event stores. One deterministic stream out.
How event sourcing scales
with Syncra
Event sourcing databases capture every state change as an immutable event. When your architecture spans multiple services, Syncra merges their streams into one.
Three steps.
From scattered signals to a single flow.
Aggregate
Connect to multiple GenesisDB event sourcing database instances across services, teams, or regions. Syncra pulls their event streams into a single, unified in-memory cache.
Unify
Events from all sources are merged into one deterministic stream, ordered by time. Every event carries its origin instance name. Full traceability across your event sourcing architecture.
Serve
Expose the merged stream through the same API you already know from GenesisDB. Every event is CloudEvents compatible. Stream and observe in real-time.
Built for event-driven
architectures
Whether you run a handful of services or a large-scale event sourcing platform, Syncra fits into your architecture without changing how your services work.
Multi-service event sourcing
When your domain is split across multiple event sourcing database instances, Syncra gives downstream consumers a consolidated view without coupling them to each source.
Cross-team event streams
Different teams own different event stores. Syncra lets you observe all of them through a single connection, filtered by the subjects you care about.
Real-time dashboards and projections
Build dashboards, read models, and reporting tools that need a live, unified feed of business events from your entire event sourcing infrastructure.
Business flow composition
Compose higher-level business flows from low-level event signals spread across independent services and bounded contexts.
Under the hood
Deterministic ordering
Events from different event sourcing instances are merged by time with stable tie-breaking by instance name and event ID. Same input, same output.
GenesisDB-compatible API
Stream and observe endpoints match the GenesisDB HTTP API. Point your existing event sourcing clients at Syncra and they just work.
In-memory, pre-serialized
Every event is JSON-serialized once at ingest time. API responses write pre-encoded bytes directly. Zero re-marshaling on the hot path.
Real-time SSE
Persistent Server-Sent Event connections to each upstream event sourcing database. New events reach observers within milliseconds.
Instance attribution
Every event carries an "instance" field identifying which event store produced it. Filter, route, or display by source.
Read-only by design
Syncra never writes to upstream event sourcing instances. It is strictly a consumer and aggregator. Nothing more.
Why event sourcing
needs aggregation
Event sourcing is an architectural pattern where every change to application state is captured as an immutable event. An event sourcing database like GenesisDB stores these events as the single source of truth. This enables full auditability, temporal queries, and reliable event replay.
As event-driven systems grow, they naturally split into multiple bounded contexts, each backed by its own event sourcing database. Orders live in one store, users in another, billing in a third. Each service owns its events, but downstream consumers often need a combined view.
GenesisDB Syncra solves this. Instead of building custom integrations between each event store and each consumer, Syncra acts as a single aggregation point. It connects to your GenesisDB instances, merges their event streams deterministically, and serves the result through the same API your teams already know.
One connection instead of many. One deterministic stream instead of scattered sources. One API for all your event sourcing data.
Ready to unify your
event streams?
GenesisDB Syncra is closed source and available for free as part of the GenesisDB product family.