this looks very cool. Rigging together your own event sourced Db is doable, but it gets a little annoying over time to keep DIYing everything, doing snapshot optimizations, etc...
one note: searchability on your query language named GQL may not be great, given the whole graphql thing.
I think the adoption hurdle will be hard unless you have a free plan that can be used for small things indefinitely. Having a hard cap on events would make me pass on this for fun side projects, which is where I would pivot later from to work projects. Just throwing that out there. This is why my last work project was supabase, I was using their free tier for some fun personal stuff.
If you have another vector for adoption that's fine too.
I'm Patric, and I just hit a major milestone - Genesis DB 1.0.(1) is officially production-ready.
Why I built this:
Existing event sourcing tools felt too heavy, opinionated, or expensive. I wanted something that matches how developers actually think about events - simple, transparent, and powerful.
What Genesis DB is:
- Event sourcing database engine written in Go
- HTTP + JSON interface (no proprietary protocols)
- Smart validation - Preconditions act as gatekeepers, enforcing business logic before writes hit the database
- Schema registration - Automatic event validation for type safety and data consistency
- Native GDPR compliance - One-command user data deletion, full data portability, built-in audit trails
- Battle-tested performance - Thousands of events/second, zero data loss, stable under load
- ...
The journey:
- Started because I love event-driven architectures but hated the tooling complexity
- A few versions, each adding features
- Now processing real production workloads across multiple industries
Want to try it?
- Free tier: 10,000 events for testing/small projects (I’m not here to be the biggest cost factor in any business. If you’ve got special requirements, let’s talk.)
- Self-host or use the managed platform (coming soon)
Amazing, well done. Having used Go for something similar can understand why you chose that for this venture. Wondering if there was anything in particular worked out for you with that decision?
this looks very cool. Rigging together your own event sourced Db is doable, but it gets a little annoying over time to keep DIYing everything, doing snapshot optimizations, etc...
one note: searchability on your query language named GQL may not be great, given the whole graphql thing.
Seems like very cool tech.
I think the adoption hurdle will be hard unless you have a free plan that can be used for small things indefinitely. Having a hard cap on events would make me pass on this for fun side projects, which is where I would pivot later from to work projects. Just throwing that out there. This is why my last work project was supabase, I was using their free tier for some fun personal stuff.
If you have another vector for adoption that's fine too.
Where can I see the architecture and the libraries used for this project?
Hey!
I'm Patric, and I just hit a major milestone - Genesis DB 1.0.(1) is officially production-ready.
Why I built this: Existing event sourcing tools felt too heavy, opinionated, or expensive. I wanted something that matches how developers actually think about events - simple, transparent, and powerful.
What Genesis DB is:
- Event sourcing database engine written in Go
- HTTP + JSON interface (no proprietary protocols)
- CloudEvents native with zero vendor lock-in
- One-command backups/restores
- Built-in Prometheus metrics & structured logging
Major features that made it to 1.0:
- Smart validation - Preconditions act as gatekeepers, enforcing business logic before writes hit the database
- Schema registration - Automatic event validation for type safety and data consistency
- Native GDPR compliance - One-command user data deletion, full data portability, built-in audit trails
- Battle-tested performance - Thousands of events/second, zero data loss, stable under load
- ...
The journey:
- Started because I love event-driven architectures but hated the tooling complexity
- A few versions, each adding features
- Now processing real production workloads across multiple industries
Want to try it? - Free tier: 10,000 events for testing/small projects (I’m not here to be the biggest cost factor in any business. If you’ve got special requirements, let’s talk.)
- Self-host or use the managed platform (coming soon)
Full docs at https://docs.genesisdb.io
Thanks for reading!
Congrats on hitting 1.0. love the focus on simplicity and real world dev workflows
Thanks a lot! That means a lot. Simplicity + real-world workflows is exactly what I wanted to nail.
Amazing, well done. Having used Go for something similar can understand why you chose that for this venture. Wondering if there was anything in particular worked out for you with that decision?