This is a fork from EventStore project: https://github.com/eventstore/eventstore

• Very simple deployment of a Windows service：ClusterNode.WindowsServices ClusterNode.DotNetCore.WindowsServices
• Using TPL Dataflow for building asynchronous event data processing pipelines.
• More efficient serialization(see https://github.com/cuteant/CuteAnt.Serialization).
• Object-Pooling.
• Faster Reflection.
• More friendly and more intuitive api for EventStore-Client.
• Better error handling with exceptions and better server connection detect.
• Auto Subscriber.
• Some Good Ideas for event subscriptions from EasyNetQ.

A Nice .NET Client API for EventStore.

Goals:

1. To make working with Event Store on .NET as easy as possible.
2. To build an API that is close to interchangable with EasyNetQ.

To publish with EasyEventStore (assuming you've already created an IEventStoreBus instance):

1. Create an instance of your message, it can be any serializable .NET type.
2. Call the Publish method on IBus passing it your message instance.

Here's the code...

var message = new MyMessage { Text = "Hello EventStore" };
bus.PublishEventAsync(message);

To subscribe to a message we need to give EasyEventStore an action to perform whenever a message arrives. We do this by passing subscribe a delegate:

bus.VolatileSubscribe<MyMessage>((sub, e) => Console.WriteLine(e.Body.Text));
bus.CatchUpSubscribe<MyMessage>((sub, e) => Console.WriteLine(e.Body.Text));
bus.PersistentSubscribe<MyMessage>((sub, e) => Console.WriteLine(e.Body.Text));

Now every time that an instance of MyMessage is published, EasyEventStore will call our delegate and print the message's Text property to the console.

To send a message, use the Send method on IEventStoreBus, specifying the name of the stream you wish to send the message to and the message itself:

bus.SendEventAsync("my.stream", new MyMessage{ Text = "Hello Widgets!" });

To setup a message receiver for a particular message type, use the Receive method on IEventStoreBus:

bus.VolatileSubscribe("my.stream", (sub, e) => Console.WriteLine("MyMessage: {0}", ((MyMessage)e.Body).Text));

You can set up multiple receivers for different message types on the same queue by using the Receive overload that takes an Action<IHandlerRegistration>, for example:

bus.VolatileSubscribeAsync("my.stream", settings,
    addHandlers: _ =>_
    .Add<MyMessage>(message => deliveredMyMessage = message)
    .Add<MyOtherMessage>(message => deliveredMyOtherMessage = message);

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.

Information on commercial support and options such as LDAP authentication can be found on the Event Store website at https://eventstore.org/support.

OS	Status
Ubuntu 14.04
Windows 8.1

Documentation for Event Store can be found here

We have a fairly active google groups list. If you prefer slack, there is also an #eventstore channel here.

The latest release packages are hosted in the downloads section on the Event Store Website

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

Event Store is written in a mixture of C#, C++ and JavaScript. It can run either on Mono or .NET, however because it contains platform specific code (including hosting the V8 JavaScript engine), it must be built for the platform on which you intend to run it.

Prerequisites

• Mono 4.6.2

Example

./build.sh {version} {configuration} {platform_override}

Parameters

• Version: Assembly Version (Required to conform to major[.minor[.build[.revision]]])
• Configuration: Build Configuration (debug or release)
• Platform Override: When Event Store is building, the build script will attempt to locate the projections library (libjs1.so) that was built for the particular platform the build script is running on. The repository has a couple of prebuilt projections libraries for various platforms such as Ubuntu-14.04, Ubuntu-16.04 and CentOS 7.2.1511. In some cases you won't need to recompile the library for the particular platform but a compatible one might be available. In these cases, the platform override can be used to let the build script know that you are happy to use one of the prebuilt ones by specifying the one it should use.

The list of precompiled projections libraries can be found in src/libs/x64

Prerequisites

• .NET Framework 4.0+
• Windows platform SDK with compilers (v7.1) or Visual C++ installed (Only required for a full build)

Example

.\build.cmd {what-to-build} -Configuration {configuration} -Version {version}

Parameters

• What to build: Specify what to build (quick, full, js1)
• Version: Assembly Version (Required to conform to major[.minor[.build[.revision]]])
• Configuration: Build Configuration (debug or release)

Prerequisites

• git

The scripts attempts to do it's best to have no dependencies from the user's point of view. If you do encounter any issues, please don't hesitate to raise an issue.

Example

./scripts/build-js1/build-js1-linux.sh {llvm-download-location} {gyp_flags}

Parameters

• LLVM Download location: The script will by default attempt to download the llvm toolchain for the OS it's running on. There can be a case where the script fails to get the correct version of the LLVM toolchain and in those cases, the user can provide the script with the download location for the toolchain.
• GYP Flags: In some cases, the user might want to provide their own GYP_FLAGS. One such case is where the user runs into the below mentioned issue. In that case this parameter can be used to pass the appropriate GYP flags.

Notes

If the scripts fails with "Failed to download LLVM. You can supply the URL for the LLVM compiler for your OS as the first argument to this script.", it is necessary to provide the script with the location where the LLVM compiler can be downloaded.

If the script fails with an gold linker error such as "ld.gold: error: /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../x86_64-linux-gnu/crti.o: unsupported reloc 42 against global symbol gmon_start" you can let it use the system linker by specifying -Dlinux_use_bundled_gold=0 as the second parameter to the script.

e.g.

scripts/build-js1/build-js1-linux.sh "" "-Dlinux_use_bundled_gold=0"

Prerequisites

• git
• Windows platform SDK with compilers (v7.1) or Visual C++ installed

Example

.\build.cmd js1

Development is on the branch aimed at the next release (usually prefixed with release-v0.0.0). The master branch always contains the code for the latest stable release.

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.

Note: Event Store 4.0.0 onwards is using a more recent version of Mono (4.6.2 at the time of writing). The information below only applies to Event Store <= 3.9.3.

There is a known issue with some versions of the Linux Kernel and Mono 3.12.1 which has been raised as an issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584. The issue manifests itself as a NullReferenceException and the stack trace generally looks like the following.

System.NullReferenceException: Object reference not set to an instance of an object
at EventStore.Core.Services.TimerService.ThreadBasedScheduler.DoTiming () [0x00000] in :0
at System.Threading.Thread.StartInternal () [0x00000] in :0

Some known good versions of the Kernel are

• 3.13.0-54
• 3.13.0-63
• 3.16.0-39
• 3.19.0-20
• 3.19.0-64
• 3.19.0-66
• >= 4.4.27

Note: Please feel free to contribute to this list if you are working on a known good version of the kernel that is not listed here.