All Projects → EventStore → Eventstore

EventStore / Eventstore

Licence: other
The stream database optimised for event sourcing

Programming Languages

C#
18002 projects
javascript
184084 projects - #8 most used programming language
shell
77523 projects
powershell
5483 projects
Dockerfile
14818 projects
HTML
75241 projects

Projects that are alternatives of or similar to Eventstore

workflow
Functional CQRS Eventsourcing Engine
Stars: ✭ 22 (-99.5%)
Mutual labels:  cqrs, eventstore, event-sourcing, eventsourcing
Eventstore
Event store using PostgreSQL for persistence
Stars: ✭ 729 (-83.41%)
Mutual labels:  event-sourcing, eventstore, database, cqrs
Bifrost
This is the stable release of Dolittle till its out of alpha->beta stages
Stars: ✭ 111 (-97.47%)
Mutual labels:  event-sourcing, eventsourcing, eventstore, cqrs
eventuous
Minimalistic Event Sourcing library for .NET
Stars: ✭ 236 (-94.63%)
Mutual labels:  cqrs, eventstore, event-sourcing, eventsourcing
Eventflow.example
DDD+CQRS+Event-sourcing examples using EventFlow following CQRS-ES architecture. It is configured with RabbitMQ, MongoDB(Snapshot store), PostgreSQL(Read store), EventStore(GES). It's targeted to .Net Core 2.2 and include docker compose file.
Stars: ✭ 131 (-97.02%)
Mutual labels:  event-sourcing, eventsourcing, eventstore, cqrs
Learning.EventStore
A framework for CQRS, Eventsourcing, and messaging that uses Redis pub/sub for messaging and offers event persistence in Redis, SQL Server, or PostgreSQL.
Stars: ✭ 58 (-98.68%)
Mutual labels:  cqrs, eventstore, event-sourcing
event-store-mgmt-ui
Event Store Management UI
Stars: ✭ 23 (-99.48%)
Mutual labels:  cqrs, event-store, eventsourcing
node-event-storage
An optimized event store for node.js
Stars: ✭ 29 (-99.34%)
Mutual labels:  cqrs, eventstore, event-sourcing
les
Go directly from an event storming to a working API: Event Markdown / Markup validation & NodeJS CQRS/ES application builder.
Stars: ✭ 48 (-98.91%)
Mutual labels:  cqrs, eventstore, eventsourcing
fmodel-ts
Functional Domain Modeling with Typescript
Stars: ✭ 41 (-99.07%)
Mutual labels:  cqrs, event-sourcing, eventsourcing
delta
DDD-centric event-sourcing library for the JVM
Stars: ✭ 15 (-99.66%)
Mutual labels:  cqrs, event-sourcing, eventsourcing
nestjs-boilerplate-microservice
Nestjs Microservice boilerplate: apply DDD, CQRS, and Event Sourcing within an event driven architecture
Stars: ✭ 270 (-93.86%)
Mutual labels:  cqrs, eventstore, eventsourcing
wolkenkit-eventstore
wolkenkit-eventstore is an open-source eventstore for Node.js that is used by wolkenkit.
Stars: ✭ 79 (-98.2%)
Mutual labels:  cqrs, eventstore, event-sourcing
Totem
Knowledge work at play
Stars: ✭ 56 (-98.73%)
Mutual labels:  cqrs, event-sourcing, eventsourcing
factcast
This project is archived. A friendly fork can be found at https://github.com/factcast/factcast/
Stars: ✭ 14 (-99.68%)
Mutual labels:  cqrs, eventstore, eventsourcing
micro
Functional prooph for microservices
Stars: ✭ 53 (-98.79%)
Mutual labels:  cqrs, event-sourcing, eventsourcing
node-cqrs
CQRS backbone with event sourcing for Node.js
Stars: ✭ 63 (-98.57%)
Mutual labels:  cqrs, eventstore, event-sourcing
Sequent
CQRS & event sourcing framework for Ruby
Stars: ✭ 400 (-90.9%)
Mutual labels:  eventsourcing, eventstore, cqrs
Netcoremicroservicessample
Sample using micro services in .NET Core 3.1 Focusing on clean code
Stars: ✭ 403 (-90.83%)
Mutual labels:  event-sourcing, eventsourcing, cqrs
Revo
Event Sourcing, CQRS and DDD framework for C#/.NET Core.
Stars: ✭ 162 (-96.31%)
Mutual labels:  event-sourcing, eventsourcing, cqrs

EventStoreDB

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

This is the repository for the open source version of EventStoreDB, which includes the clustering implementation for high availability.

Support

Information on support and commercial tools such as LDAP authentication can be found here: Event Store Support.

CI Status

Build

Build

Build

Build

Build

Documentation

Documentation is located in the docs folder. It's orchestrated in the separate documentation repository. It's available online at https://developers.eventstore.com/.

Read more in the documentation contribution guidelines.

Community

We have a community discussion space at Event Store Discuss. If you prefer Slack, there is also an #eventstore channel in the DDD-CQRS-ES Slack community.

Release Packages

The latest release packages are hosted in the downloads section on the Event Store website: Event Store Downloads

We also host native packages for Linux on Package Cloud and Windows packages can be installed via Chocolatey (4.0.0 onwards only).

Building EventStoreDB

EventStoreDB is written in a mixture of C#, C++ and JavaScript. It can run on Windows, Linux and macOS (using Docker) using the .NET Core runtime. However, the projections library (which uses the V8 javascript engine) contains platform specific code and it must be built for the platform on which you intend to run it.

Windows / Linux

Prerequisites

Build EventStoreDB

Once you've installed the prerequisites for your system, you can launch a Release build of EventStore as follows:

dotnet build -c Release src

The build scripts: build.sh and build.ps1 are also available for Linux and Windows respectively to simplify the build process.

To start a single node, you can then run:

dotnet ./src/EventStore.ClusterNode/bin/x64/Release/net5.0/EventStore.ClusterNode.dll --insecure --db ./tmp/data --index ./tmp/index --log ./tmp/log -runprojections all --startstandardprojections --EnableAtomPubOverHttp

Note: The build system has changed after version 5.0.5, therefore the above instructions will not work for older releases.

Running the tests

You can launch the tests as follows:

dotnet test src/EventStore.sln

Building the EventStoreDB Clients

The client libraries are located in their own repositories, refer to their specific instructions.

gRPC clients:

TCP clients:

Note: the TCP protocol is being phased out.

Building the EventStoreDB web UI

The web UI repository is a git submodule of the current repository located under src/EventStore.UI.

The web UI is prebuilt and the files are located in src/EventStore.ClusterNode.Web/clusternode-web. However, if you still want to build the latest web UI, there is a parameter in the build.sh ([<build_ui=yes|no>]) and build.ps1 (-BuildUI) scripts to allow you to do so.

Building the Projections Library

The list of precompiled projections libraries can be found in src/libs/x64. If you still want to build the projections library please follow the links below.

Contributing

Development is done on the master branch. We attempt to do our best to ensure that the history remains clean and to do so, we generally ask contributors to squash their commits into a set or single logical commit.

If you want to switch to a particular release, you can check out the tag for this particular version. For example:
git checkout oss-v6.0.0-preview1

Read more in the contribution guidelines.

Proto Changes

If you update the protos, continuous integration will fail. After ensuring the proto change is backwards compatible, please run ./protolock.sh commit at the root of this repository.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].