Marten VS message-db

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/

I’m addition to the alternatives mentioned, here’s another Postgres-only ES implementation: https://github.com/message-db/message-db

Thalo is a new Rust library that provides a runtime for WASM-based event sourcing. With Thalo, developers can compile their aggregates and components into WASM modules and use them in the runtime to handle commands and persist events to an event store. The library is built on top of Wasmtime and Message DB, and uses the ESDL schema language to define aggregates. While Thalo is not yet ready for real-world use, it has the potential to make event sourcing more accessible to a wider range of languages that compile to WASM, allowing for a language-agnostic runtime. Give it a try and let us know what you think! https://github.com/thalo-rs/thalo

Its built on top of Wasmtime for wasm execution, and MessageDb which is a message store for Postgres.

We are using message db which is uses postgres under the hood, and provides a few useful postgres functions. We use it with `postgres-simple` and have a small internal library. However my colleague is working on abstracting our logic and open sourcing into a library here: https://github.com/Disco-Dave/message-db

Check out MessageDB https://github.com/message-db/message-db. It's basically Postgres and can be installed into any Postgres DB.

Trying a new language or framework is fun experiments that you spend a few hours on. I have been enjoying implementing Message DB[0] in a hobby project. My current job is not in programming, and not looking for one.

[0]https://github.com/message-db/message-db