2 مستودعات
Databases that store events as the immutable source of truth, preserving order and structure for audit trails and event-driven architectures.
Distinct from Database Event Listeners: None of the candidates match: they cover UI event streams, DOM event handling, or database event triggers/listeners, not the concept of an event-native database itself.
Explore 2 awesome GitHub repositories matching data & databases · Event-Native Databases. Refine with filters or upvote what's useful.
KurrentDB is an event-native database designed for event sourcing and event-driven architectures. It stores application state as an immutable, ordered sequence of events rather than updating rows in place, preserving full history for audit, replay, and distributed consistency. The database combines event storage with real-time streaming and a built-in JavaScript projection engine that transforms and aggregates event streams into materialized views. The system provides official gRPC client libraries for Python, Node.js, Java, .NET, Go, and Rust, enabling multi-language application development
Stores application state as an immutable, ordered sequence of events for audit, replay, and event-driven architectures.
KurrentDB is an event-native database designed for event sourcing and event-driven architectures. It stores events as immutable, ordered records in streams, preserving a complete audit trail and enabling temporal queries. The database uses gRPC for all client-server and inter-node communication, providing efficient binary serialization and bidirectional streaming, and supports atomic multi-stream writes that ensure consistency across multiple streams in a single transaction. The database distinguishes itself with a built-in JavaScript projection engine that transforms, filters, and aggregates
Stores events as immutable, ordered records in streams, preserving a complete audit trail.