We have collection of more than 1 Million open source products ranging from Enterprise product to small libraries in all platforms. We aggregate information from all open source repositories. Search and find the best for your needs. Check out projects section.
EventStore - The open-source, functional database with Complex Event Processing in JavaScript.
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.
cqrs eventsourcing eventstore event-sourcing event-store databaseEquinoxProject - Full ASP.NET Core 2.0 application with DDD, CQRS and Event Sourcing
Also you can run the Equinox Project in Visual Studio Code (Windows, Linux or MacOS).
equinox cqrs architecture asp-net-core aspnet-core asp-net-core-mvc ddd ddd-architecture event-sourcing eventstore automapper ef-core asp-net-identity mediatr visual-studio fluentvalidation onion-architecture clean-code swagger aspnetcoreEventFlow - Async/await first CQRS+ES and DDD framework for .NET
EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our getting started guide, the do’s and don’ts and the FAQ.
eventsourcing cqrs async-await eventstore events elasticsearch rabbitmq sagas domain-driven-design ddd c-sharp cqrs-es framework nuget netstandardlaravel-event-projector - Event sourcing for Artisans π½
Event sourcing is to data what Git is to code 1. Most applications have their current state stored in a database. By storing only the current state a lot of information is lost. You don't know how the application got in this state. Event sourcing tries to solve that problem by saving all events that happen in your app. The state of your application is built by listening to those events.
laravel event-sourcing events eventstoreeventstore - CQRS event store using PostgreSQL for persistence
CQRS event store implemented in Elixir. Uses PostgreSQL as the underlying storage engine. Requires Elixir v1.5 and PostgreSQL v9.5 or newer.
cqrs eventstore elixir event-sourcing postgresql database cqrs-esnode-eventstore - EventStore Implementation in node.js
Node-eventstore is a node.js module for multiple databases. It can be very useful as eventstore if you work with (d)ddd, cqrs, eventsourcing, commands and events, etc.
event-sourcing eventstream eventstore nodejs domain-driven-design cqrs ddd (d)ddd eventsourcing mongodb redis tingodb azure azuretable inmemory elasticsearchevent_bus - :surfer: Traceable, extendable and minimalist **event bus** implementation for Elixir with built-in **event store** and **event watcher** based on ETS
Traceable, extendable and minimalist event bus implementation for Elixir with built-in event store and event watcher based on ETS.
elixir eventbus event-sourcing eventstoreEventStore.Akka.Persistence - Event Store Journal for Akka Persistence
Akka Persistence journal and snapshot-store backed by Event Store.Akka serializes your messages into binary data by default. However you can add your own serializer to serialize as JSON, But make sure you extend akka.persistence.eventstore.EventStoreSerializer rather then akka.serialization.Serializer. And in case you are really going to serialize as json, please specify ContentType.Json, it will allow you to use projections.
akka-persistence eventstore akka cqrsnodeCQRS - CQRS, EventSourcing, (DDDD) Sample in node.js
the source code is well documented to understand the core principles. As of today i know of three implementations for doing (D)DDD / CQRS in node.js. Building a codebase for production is a whole different thing to doing a little show case / demo code. If it can break - it will break.
cqrs eventstore ddd eventsourcinghyperemitter - Horizontally Scalable EventEmitter powered by a Merkle DAG
HyperEmitter is a horizontally scalable and persistent EventEmitter powered by a Merkle DAG. (Yes, it's like a blockchain). In other contexts, this concept is also called an EventStore. HyperEmitter uses protocol-buffers, specifically mafintosh's implementation, for handling message schemas, although custom codecs are also supported. The example below can be found and ran from the examples folder; it demonstrates how to connect two HyperEmitters together and how they both receive all messages sent.
event store eventstore emitter merkle dagpg-events - Use Postgresql as an Event Store for Node.js development
Use Postgresql as an Event Store for Node.js development
postgres pg postgresql eventstore projectionsnodejs-EventStore - Node.js driver for Event Store
It has HTTP and TCP client interfaces -- this project implements the TCP interface in Node.js in an async fashion.
cqrs ddd eventsourcing eventstoreeventsource-api - Provides an eventsourcing high level API.
Home of an attempt to formalize eventsourcing. We use stack to build project under this repository.
eventsourcing eventstoreeventstore - EventStore Haskell TCP Client
Note: If you use this client version >= to 1.1, it will only supports EventStore >= 4.0.0. Tests are available. Those assume a server is running on 127.0.0.1 and 1113 port.
haskell eventsourcing eventstore database-driver tcp-clientlambda-database-experiment - Experimental event store database entirely written in Haskell
Experimental event store database entirely written in Haskell. The main goal is learning. Database programming is full of interesting algorithms and challenges. There is no plan for going production ready but it will be definitely cool if it happens someday. This project assumes a 64bits Unix system and the build tool stack installed. The project is developped mainly on Mac OSX and Linux based distributions. For now, nothing prevents the project from being built on Windows. That being said, Windows will never be officially supported.
haskell database eventstoregoes - Go Event Store TCP Library
GOES is an Event Store golang TCP Library for Go. Licenced under MIT.
geteventstore tcp protobuf eventstorememstate - In-memory event-sourced ACID-transactional distributed object graph engine for
In-memory event-sourced ACID-transactional replicated object graph engine. What? Can you say that again? Ok, it's an application server that keeps all your data in RAM. It runs without a database because all the transactions are recorded in a log and used to restore the state of the application at startup or when setting up a replica. You define the object model, commands and queries using C#. Besides being very simple Memstate is also very fast and will outperform any relational database. Your data fits in RAM. Moving bits and pieces back and forth between disk and memory is slow, difficult to maintain and error prone. Use Memstate to structure and manage your data in-memory, providing transparent persistence, high performance, high availability, concurrency control and transactions with strong ACID guarantees.
event-sourcing eventstore origodb microservices graph in-memory-databaseevent_bus_postgres - π Postgres event store for event_bus
Listen and save event_bus events to Postgres. Module docs can be found at https://hexdocs.pm/event_bus_postgres.
genstage eventbus elixir eventstore postgresrxeventstore - RxEventStore is a module for persisting and querying data using the Event Sourcing pattern and RxJs
RxEventStore is a module for persisting and querying data using the Event Sourcing pattern and RxJs. Redis and PostgreSQL are currently supported as data stores. The redis driver also has the ability to project the event log onto any other redis data structure.
rxjs eventstore eventsourcing redis postgresqlevent-sourcing-castanha - An Event Sourcing service template with DDD, TDD and SOLID
Castanha is a Service Template for helping you to build evolvable, adaptable and maintainable Event Sourcing applications. It follows the principles from the Clean Architecture book and has a Domain built on Domain-Driven Design. It is easy for you to start your new microservice based on its guidelines and patterns. The implementation result of the Clean Architecture is a software that encapsulate Business Rules in Use Cases and the Enterprise Rules in Entities. Also the Use Cases are independent from details like User Interface, Data Access, Web Server or any external agency.
event-sourcing event-driven eventstore ddd ddd-patterns ddd-sample cqrs solid microservice dotnetcore kafka mongodb webapi bearer-authentication cqs clean-architecture clean-code tdd domain-driven-design
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.
