The stream database optimised for event sourcing
-
Updated
Sep 5, 2020 - C#
{{ message }}
The stream database optimised for event sourcing
Real-time FX trading showcase by Adaptive.
Microservice native message and event store for Postgres
PHP 7.4 EventStore Implementation
Stream Store library targeting RDBMS based implementations for .NET
Go - CQRS / Event Sourcing made easy - Go
A Node.js CQRS and Event Sourcing Microservice Example Using Nest.js, Event Store, and Swagger
Provides basic functionality for event sourced aggregates.
Event Sourcing and CQRS in practice.
NEventLite - An extensible lightweight library for .NET that manages the Aggregate lifecycle in an Event Sourced system. Supports Event and Snapshot storage providers like EventStore/Redis or SQL Server. Built with dependency injection in mind and seamlessly integrates with AspNetCore.
PDO implementation of ProophEventStore http://getprooph.org
PHP 7.4 Event Store Client Implementation
Event Store Symfony Bundle
Event Sourcing and Microservices Stack for Ruby
A State Machine Eventstore using PostgreSQL schemata defined by Petri-Nets
Event Store backed by Azure Cosmos DB
JS client library for connecting to Event Store over TCP/IP
NestJS CQRS module for EventStore.org. It requires @nestjs/cqrs
Prooph. How to use.
PHP 7.2 Event Store HTTP Client Implementation
Event Store Management UI
Prooph EventStore HTTP API
Standard projections to use with Prooph EventStore
Open Source Cross Platform EventStore(see https://eventstore.org/) Solution based on .NET Core 3.1 and Netty(https://github.com/cuteant/dotnetty-span-fork)
Java Event Store FoundationDB Layer
Event store library for .NET Core based on rdbms persistance.
Add a description, image, and links to the event-store topic page so that developers can more easily learn about it.
To associate your repository with the event-store topic, visit your repo's landing page and select "manage topics."
Currently the client can not ask the server to stop sending events from a specify stream. It is because the server does not currently globally know which client is subscribed to which stream. This is also why clients could, by mistake or not, subscribe multiple times to the same stream and receive events multiple times.