EventSourcing.NodeJS VS Marten

Thanks for the response, I found materials for event sourcing with node.js examples (here) and will read more about it. Before diving in, the things you say sounds crazily complex, so one of the two: or it's in fact easier than I'm imagining, or it must be justified by crazily complex system which becomes a hell to maintain.

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)

Check out Marten for a fully fleshed out implementation https://github.com/JasperFx/marten

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/

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.

You're better off using Postgres (has JSON columns.) If you want a more "document" oriented experience, use Marten: https://martendb.io/

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.

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.

Not to be confused with the C# document database built on Postgres.

https://martendb.io/