2 repository-uri
Accepting a write to a stream only when the stream is in a specific state, such as being soft-deleted.
Distinct from Atomic Multi-Stream Writes: Distinct from Atomic Multi-Stream Writes: focuses on conditional writes based on stream state, not atomicity across multiple streams.
Explore 2 awesome GitHub repositories matching data & databases · Conditional Stream Writes. 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
Accepts writes to a stream only when it is in a specific state, such as being soft-deleted.
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
Accepts write operations only when a target stream is in a specified state, such as soft-deleted.