message-db VS thalo

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

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

Over the past couple of months I've rewritten a project of mine from scratch called Thalo. https://github.com/thalo-rs/thalo

Interesting! Thanks for sharing. I can see how macros can be heavy, but yours was pretty light IMO. Comparing with the current example, the current one has basically the same code, plus the edsl code that looks like a header (if Rust ever had C's .h or OCaml's .mli files). Which isn't necessarily a bad thing though.