Marten
.NET Transactional Document DB and Event Store on PostgreSQL (by JasperFx)
Event Store
EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures (by EventStore)
Our great sponsors
Marten | Event Store | |
---|---|---|
23 | 5 | |
2,662 | 5,073 | |
2.1% | 0.7% | |
9.8 | 9.5 | |
4 days ago | 5 days ago | |
C# | C# | |
MIT License | GNU General Public License v3.0 or later |
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.
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.
- Marten – .NET Transactional Document DB and Event Store on PostgreSQL
-
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
-
Is anyone using Dapr
We are using ExtCore here to make our app modular: https://extcore.net/, and MartenDB for event store (which is surprisingly VERY simple) : https://martendb.io/
-
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.
-
This article is covering the potential problems you will face when using MongoDB for typical relational tasks.
You're better off using Postgres (has JSON columns.) If you want a more "document" oriented experience, use Marten: https://martendb.io/
-
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.
- Event-driven projections in Marten explained
-
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.
https://martendb.io/
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.
-
Event Store State of the Art
I've been doing some research and found this: https://github.com/EventStore/EventStore
-
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.
What are some alternatives?
When comparing Marten and Event Store you can also consider the following projects:
MongoDB - The MongoDB Database
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
RavenDB - ACID Document Database
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
FluentMigrator - Fluent migrations framework for .NET