2 ms·
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 t
by patriceckhart 1y ago
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 https://docs.genesisdb.io
Thanks for reading!
- capestart 1y agoCongrats on hitting 1.0. love the focus on simplicity and real world dev workflows
- patriceckhart 1y agoThanks a lot! That means a lot. Simplicity + real-world workflows is exactly what I wanted to nail.
- goloroden 1y agoJust a little hint: Read the other comments as well…
- NomDePlum 1y agoAmazing, 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?
- goloroden 1y agoJust a little hint: Read the other comments as well…
- patriceckhart 1y agoI've been using Go for some time now. I've never programmed with Rust before, and it seemed appropriate to use Go for this project. In my initial prototypes of an event sourcing system that I experimented with last year, I used PHP (yes PHP) with either PostgreSQL or MySQL and a few other things. A major advantage of Go is its backward compatibility, which certainly makes maintenance easier.