Event Store
EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures (by EventStore)
Marten
.NET Transactional Document DB and Event Store on PostgreSQL (by JasperFx)
Our great sponsors
Event Store | Marten | |
---|---|---|
5 | 23 | |
5,052 | 2,643 | |
0.9% | 3.0% | |
9.5 | 9.8 | |
about 19 hours ago | 4 days ago | |
C# | C# | |
GNU General Public License v3.0 or later | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Event Store
Posts with mentions or reviews of Event Store.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-11.
-
if you had to restart at 0 knowledge what would you do?
C#: In Europe, Java is still strong but many trading firms use C# because of the strong Microsoft culture in Europe, as well as because of strongly supported C# libraries like say EventStore, which tends to be used for the matchmaking engines for stock exchanges (especially that exchange matchmaking problem is basically SMR). And skimming over the code, it has Paxos implemented too, making it good for dealing with partial failures (failover), essential for any HFT/trading firm. C#'s also the biggest ecosystem that many of the breakthrough java tech mentioned earlier was first ported to.
- Call for Help - Open Source Datom/EAV/Fact database in Rust.
-
Event sourcing two years later (almost)
Support for eventstore.com eventstore. esdb
-
3 reasons to adopt Event Sourcing
Where's the catch, then? Well, there's a couple of catches, in fact. First of all, in a distributed setting, appending data to a log isn't that easy. First, you need to make your log distributed. Again, Kafka/Cassandra/EventStore make this possible, however, whenever you start dealing with distributed data, you‘re introducing new operational and implementation complexity.
Marten
Posts with mentions or reviews of Marten.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-06.
-
Dapper vs. Entity Framework With Postgres
Id recommend trying out MartenDb. It's not really a PostgreSQL ORM, it actually uses Postgres more as a document database via jsonb. But it's excruciatingly easy to use and schema updates are a breeze (and largely automatic)
-
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store
Check out Marten for a fully fleshed out implementation https://github.com/JasperFx/marten
-
Yet another embedded DB (kind of)
I always loved Marten, it is so simple to use and yet powerful. If you are unfamiliar with it, it is a data access library (like an ORM) that is using JSON serialization and LINQ to store and query data from/to Postgres. It basically turns Postgres into document DB. Comparing it to EF, Marten doesn't require migrations since it stores documents.
-
Self-Paced Kit: Introduction to Event Sourcing with Node.js and TypeScript
For that part, the samples use EventStoreDB (https://www.eventstore.com/), which is the only mature event store I know in Node.js land. Event Sourcing allows using any database as backing storage. I'm co-maintainer of the Marten (https://martendb.io/), which is a .NET library that allows using Postgres as event store and document db.
-
CQRS is simpler than you think with C#11 and .NET 7!
Then you should check out Marten (https://martendb.io/). Our intention is to remove the boilerplate, we're using Postgres e having the built-in projections.
-
Marten, a Crystal web framework that makes building web apps productive and fun
Not to be confused with the C# document database built on Postgres.
-
Which libraries/frameworks are you using for Event Sourcing?
Haven't tried it myself yet, but they were in .NET foundation, them left after some drama: https://martendb.io/
-
Straightforward Event Sourcing with TypeScript and NodeJS
Thanks for the feedback and the link! Indeed that looks similar. I think that too many NodeJS tooling is made by C# or Java devs bringing their OOP habits. In my opinion, TypeScript and NodeJS development shines the most when you're cutting all the boilerplate and keeping things simple. Functional composition helps in that. I'm also coming from the .NET world and am co-maintainer of the Postgres-based library: https://martendb.io/, but I try to keep my OOP habits on a leash ;) Out of curiosity, how are you dealing with the eventual consistency and the read-your-own-writes guarantee on MongoDB in your library?
-
.NET build tool using Bullseye and SimpleExec
I personally advocate Bullseye in combination with SimpleExec as a build tool for .NET projects due to its sheer simplicity by providing a bare bones API to define the tasks and their dependent tasks in plain C# code. Both these libraries are build by Adam Ralph. It does not enforce any specific model or structure to write your build tasks. When someone runs through the build script, it is fairly straight forward to understand whats going on. We use this build tool setup for Marten for both local dev and CI build tasks and has worked well so far. Also many OSS projects have adopted it.
-
GitHub action to publish .NET packages to NuGet
I have been a co-maintainer of .NET OSS library Marten and largely involved in taking care of the DevOps stuff pertaining to CI pipeline, build and docs system. In the early days, the build was driven using a RAKE build script written by Jeremy Miller, our lead dev and creator of Marten. NuGet packages were published from the local dev machine after confirming that we had bumped up the versions of the packages in preparation for the release. Apparently, this being a manual step, we publish the NuGet packages but sometimes tend to forget tagging and creation of release in GitHub (you know how an OSS author life is around managing day job and doing open source work).
What are some alternatives?
When comparing Event Store and Marten you can also consider the following projects:
MongoDB - The MongoDB Database
RavenDB - ACID Document Database
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
Streamstone - Event store for Azure Table Storage
Yessql - A .NET document database working on any RDBMS
Apache Ignite - Apache Ignite
efcore.pg - Entity Framework Core provider for PostgreSQL
Firebase.Net - C# wrapper over Firebase database REST API
Apache Cassandra - Mirror of Apache Cassandra