Event Sourcing - .NET

This repository contains a starter pack for Event Sourcing in .NET It is a production grade starting point for your own event sourced application. The starter pack has everything you need to get started with event sourcing, including an event store, a projection store, and an event bus.

This starter pack implements a simple example for a Cooking Club Membership. But you're meant to replace this example with your own application.

Getting Started

To run this application you need Docker. Once you have Docker installed, please clone the code, navigate to the local-development/scripts folder.

git clone git@github.com:ambarltd/event-sourcing-dotnet.git
cd event-sourcing-dotnet/local-development/scripts/linux # if you're on linux
cd event-sourcing-dotnet/local-development/scripts/mac # if you're on mac
./dev_start.sh # start docker containers
./dev_demo.sh # run demo

You can then open your browser to:

• http://localhost:8080 to ping the backend
• http://localhost:8081 to view your event store
• http://localhost:8082 to view your projection store

How to Develop Your Own Application

Assuming you know event sourcing theory, developing on this application will feel very natural. Otherwise, don't worry - Ambar offers a free 1 day Event Sourcing course here.

To get a quick understanding of how this application works, please read the domain code in Domain/, the abstractions provided in Common/, and the README files also in Common/. With that reading done, here's a full picture:

1. Domain/: where you define aggregates, events, commands, queries, projections, and reactions. You will spend most of your time here.
2. Common/: a set of event sourcing abstractions. You will rarely need to edit files here, except for having to update the Serializer and Deserializer classes in Common/SerializedEvent/ whenever you add or remove events.
3. Program.cs: contains the application's startup file as well as configuration of your dependency inection container. You will need to edit this file to register or unregister services as you see fit (controllers, repositories, etc.).

When developing your application for the fist time, we recommend you keep the Cooking Club Membership code as an example you can quickly navigate to. Once you have implemented several commands, queries, projections, and reactions, delete the Cooking Club Membership code. This will require you to delete its code in Domain, serialization logic in Common/serializedEvent, and relevant services in Program.cs.

Additional Scripts

Whenever you build a new feature, you might want to restart the application, or even delete the event store and projection store. We have provided scripts to help you with that.

cd event-sourcing-dotnet/local-development/scripts/linux # if you're on linux
cd event-sourcing-dotnet/local-development/scripts/mac # if you're on mac
./dev_start.sh # starts / restarts the application.
./dev_start_with_data_deletion.sh # use this if you want to delete your existing event store, and projection db, and restart fresh.
./dev_shutdown.sh # stops the application

Deployment

To deploy this application to a production environment, you will simply need to build the code into a docker image, and deploy it to your cloud provider. We have provided infrastructure starter packs for various clouds in this repository.

Support

If you get stuck, please feel free to ask questions in the #event-sourcing channel of our Slack community. Or if you need further help like a free private walkthrough, simply book one here.