Displaying 1 to 14 from 14 results

EventStore - The open-source, functional database with Complex Event Processing in JavaScript.

  •    CSharp

The open-source, functional database with Complex Event Processing in JavaScript.This is the repository for the open source version of Event Store, which includes the clustering implementation for high availability.

message-db - Microservice native message and event store for Postgres

  •    Shell

A fully-featured event store and message store implemented in PostgreSQL for Pub/Sub, Event Sourcing, Messaging, and Evented Microservices applications. An event sourcing and Pub/Sub message store built on Postgres for simple cloud or local hosting. A minimalist implementation of the essential features of tools like Event Store or Kafka, with built-in support for messaging patterns like Pub/Sub, and consumer patterns like consumer groups.

event-store - PHP 7.1 EventStore Implementation

  •    PHP

PHP 7.1 EventStore Implementation. Prooph Event Store is capable of persisting event messages that are organized in streams. Prooph\EventStore\EventStore itself is a facade for different persistence adapters (see the list below) and adds event-driven hook points for Prooph\EventStore\Plugin\Plugins which make the Event Store highly customizable.

MeiliES - A Rust based event store using the Redis protocol

  •    Rust

MeiliES is an Event Sourcing database that uses the RESP (REdis Serialization Protocol) to communicate. This way it is possible to create clients by reusing the already available protocol. For example, it is possible to use the official Redis command line interface program to communicate with MeiliES. There is a release blog post if you want to know more. An event store is like a Kafka or a Rabbit MQ but it stores events on disk indefinitely. The first purpose of the server is to publish events of a stream to all subscribed clients, note that events are saved in reception order. A client can also specify from which event number (incrementing) it wants to read, therefore it is possible to recover from crashing by reading and reconstructing a state with only new events. Keep in mind that a message queue is not made for event-sourcing.




eventhus - Go - CQRS / Event Sourcing made easy - Go

  •    Go

CQRS/ES toolkit for Go. CQRS stands for Command Query Responsibility Segregation. It's a pattern that I first heard described by Greg Young. At its heart is the notion that you can use a different model to update information than the model you use to read information.

SQLStreamStore - Stream Store library targeting RDBMS based implementations for .NET

  •    CSharp

A stream store library for .NET that specifically target SQL based implementations. Typically used in Event Sourced based applications. Building requires Docker. Solution and tests are run on a linux container with .net core leveraging SQL Server and Postgres as sibling containers.

event-sourcing - Provides basic functionality for event sourced aggregates.

  •    PHP

This library will receive support until December 31, 2019 and will then be deprecated. You can install ProophEventSourcing via composer by adding "prooph/event-sourcing": "^5.0" as requirement to your composer.json.

event-store-bus-bridge - Marry CQRS with Event Sourcing

  •    PHP

This package acts as a glue component between prooph/service-bus and prooph/event-store. This library will receive support until December 31, 2019 and will then be deprecated.


event-store-client - PHP 7.2 Event Store Client Implementation

  •    PHP

PHP 7.2 Event Store Client Implementation. Prooph Event Store Client supports async non-blocking communication via TCP to EventStore. In the future, there will be also a server implementation written in pure PHP using Postgres (maybe also MySQL) as backend.

event-store-http-api - Prooph EventStore HTTP API

  •    PHP

Prooph Event Store is capable of persisting event messages that are organized in streams. Prooph\EventStore\EventStore itself is a facade for different persistence adapters (see the list below) and adds event-driven hook points for Prooph\EventStore\Plugin\Plugins which make the Event Store highly customizable. The HTTP API is a standalone software that exposes event streams via HTTP protocol.

event-store-mgmt-ui - Event Store Management UI

  •    Javascript

The ES-Mgmt-UI is under heavy development. If you are interested you can install it and explore it of your own. More information is provided later when we have a first working version. Based on wmonk/create-react-app-typescript but it's ejected for customization.

event-store-symfony-bundle - Event Store Symfony Bundle

  •    PHP

Installation of this Symfony bundle uses Composer. For Composer documentation, please refer to getcomposer.org. Run composer require prooph/event-store-symfony-bundle to install prooph event-store-symfony-bundle.

pdo-event-store - PDO implementation of ProophEventStore http://getprooph.org

  •    PHP

For MySQL you need server version >= 5.7.9. For Postgres you need server version >= 9.4.

standard-projections - Standard projections to use with Prooph EventStore

  •    PHP

The standard projections are some kind of event-indexing, so you can retrieve events from all streams at once (AllStreamProjectionRunner), by category (CategoryStreamProjectionRunner) or by message name (MessageNameStreamProjectionRunner). See docs for more information. Documentation is in the doc tree, and can be compiled using bookdown.






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.