We have already discussed this. I think branches are a good idea, although we need to look at how they work first. For your GenesisDB, I would really like a "softer" mode so that individual types and events can be removed during development. Perhaps that could also be done with branches.

The 500 MB for storage is a bit of an overestimate. We've been using GenesisDB for a few months now and only have a few MB of storage used. :)

It would be complete with a few examples in the common programming languages. Otherwise, it's good.

That's really cool. Is it recommended to use this for production as well? Specifically, if the Mac hosts the production instances of GenesisDB?

I've thought about that. Do you actually see a real use case for running a Mac as a server? Maybe if you're hosting an internal-only app and the Mac acts as the local database server.

Hello ...

I just finished my first internal project using Genesis DB (https://genesisdb.io)

The app uses a full CQRS + Event Sourcing setup, and Genesis DB worked really well as the event store. It felt lightweight but still powerful enough for production-style use.

I’m curious, has anyone else here already built one or more projects with Genesis DB? Would love to hear your experiences, especially around event modeling, projections, or performance in real-world scenarios.

Markus

Very cool! Could easily be a 1.0.0 already. Works flawlessly so far with the provided examples.

Thank you!

Genesis DB delivers everything you could wish for. Thanks for your incredible work!!! I can recommend it to anyone seriously exploring event sourcing.

Thank you very much! I'm glad you like Genesis DB!