HNHacker News
TopNewBestAskShowJobs

patriceckhart

83 karma · joined August 12, 2025

submissionscomments
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
I've experimented quite a bit and I'm familiar with some of those concepts, in fact, I even looked at them early on in development. But my goal was to build more than just a wrapper around SQL.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
One approach is to keep track of the ID of the last consumed event and use that as the starting point for rehydration. That way, even after a migration or failover, the stream can resume efficiently without replaying the entire history.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
Event sourcing doesn't directly address this. However, the "undo" functionality is not a feature of event sourcing itself, but rather something your application needs to implement. Sure, you can implement that functionality without event sourcing, but it becomes problematic if you decide to add it later.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
I've definitely taken inspiration from some great ideas out there, but Genesis DB is built on my own design choices and implementation. The earlier concepts behaved quite similarly, with the main difference being that back then I hadn't implemented the CloudEvents standard or event hash-chaining yet. I later found both to be really valuable additions. The idea of event chaining isn't new for example, I just hadn't had it on my radar for very long.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
I'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.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
Thanks a lot! That means a lot. Simplicity + real-world workflows is exactly what I wanted to nail.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
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!

← PreviousPage 2 of 2