A simple EventStore that sits on top of your existing relational database
You want to use event sourcing, but you don't want to (or aren't allowed to) host a completely new system in your production environment. You have a relational database already, so why not use that?
RdbmsEventStore is intended to provide some basic functionality for event sourcing on top of a relational database. This is, naturally, going to be less optimal for event sourcing than using a custom-built event store like Event Store, or even a document database, so if you're at liberty to choose such a product, it might serve you better.
On the other hand, if - for some reason - you need to build your event store on your existing stack, with a relational database and a .NET application, this package is for you. This project sprung out of just such a situation.
This project is still in early beta stage.
It sprung out of just such a situation - if I wanted an event store, I had to build it on top of Microsoft SQL Server. As such, I'm using it in code that is (or will soon be) in production - but I don't recommend anyone to do the same (yet) unless you've read and understood all the code in the project. If you have, Pull Requests are warmly welcome :)
All documentation is in the project wiki.