@event-driven-io/emmett v0.9.0

Emmett - vent Sourcing development made simple

Nowadays, storage is cheap, but the information is priceless.

Event Sourcing, contrary to the standard approach, keeps all the facts that happened in our system. To do that, it needs an event store: a database designed for its needs.

This project aims to experiment with an opinionated Event Sourcing framework based on my experience working on Marten and EventStoreDB.

Take your event-driven applications back to the future!

FAQ

Is it production-ready?

Nope.

Will it be?

Maybe.

Why Node.js?

I like its minimalistic approach and flexibility, plus TypeScript is an excellent language with its shapeshifter capabilities. Plus, I've been asked if I could deliver such a store for Node.js.

Why Emmeett?

Because.

What features it has?

Currently, none, but that will change.

What features will it have?

We'll see, but for sure, I'd like to have the following:

• atomicity of the stream append operations,
• reading your writes,
• subscriptions based on Postgres logical replications,
• Postgres partitioning,
• running it serverless or on the web with SQLite,
• streaming data through HTTP API (and enabling integration scenarios through it).
• defining event transformations and projections with WebAssembly,
• build-in read models based on the JSON capabilities of Postgres and SQLite.

Would it be a competitor to other stores?

Probably not. For now, I'd like to have a safe playground to have fun and try out new ideas. Still, what I deliver, I expect to be safe to use on a small scale.

Why there's no license?

Because I'm unsure when this will end, and I don't want to expose it as an MIT license from the beginning.

Support

💖 If you'd like this initiative or want to use it potentially. Feel invited you join the group of my 👉 Github Sponsors.

GitHub ⭐'s won't pay the bills, so any help is more than welcome!