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!

Where can I see the architecture and the libraries used for this project?

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.

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.

Congratulations! I don’t think the db engine is open source. Any plans to do that?

Why not just hook up postgres to something like https://github.com/cpursley/walex or any of the other libraries like Debezium, https://sequinstream.com? Isn't postgres enough?

tbh – this pretty much looks like they straight-up copied another database that dropped earlier this year. looks like GenesisDB grabbed all its ideas from here:

https://hub.docker.com/r/thenativeweb/eventsourcingdb

take a look and see for yourself… #copycat

Nobody tell Greg Young!

Hi there,

I’m one of the creators of EventSourcingDB, and the CTO of the native web (the company behind EventSourcingDB).

Because of ongoing legal investigations I can’t comment any further, but I’d like to provide you with some links, so you can see for yourself:

https://www.eventsourcingdb.io

https://docs.eventsourcingdb.io

https://hub.docker.com/r/thenativeweb/eventsourcingdb

https://www.cqrs.com

https://www.eventsourcing.ai

Really? You built this bc “tools felt too heavy, opinionated, or expensive” — LOL… or just bc there was such a nice blueprint you could use for inspiration…?!

Here is the original:

https://www.eventsourcingdb.io

One of the big issues I’ve always found with all streaming services is rehydration post migration or for HA or failover.

Has this group done testing for how long it takes for different sizes of streams to rehydrate?

how does it differ from timescale db?

Event sourcing gives you all the technical overhead of replayable transactions while giving your end-users none of the benefits (e.g. undo/redo). It's purely an infrastructure-level feature that only makes auditors and sysadmins happier.

What does

"Logs like a Philosopher."

Mean? Did you mean sage? I dont want my logs to make me contemplate the meaning of life.

I find GenesisDB difficult in several respects. On the one hand, there is its similarity to EventSourceDB and the fact that it is almost a 1:1 copy, for example in terms of the query language. On the other hand, the performance of GenesisDB is anything but acceptable, i noticed some query language bugs and the PHP and JavaScript SDKs are offered without testing. But now comes the critical point: it's a one-man show, without open source, which raises the question: why should as a person or as a company rely on GenesisDB for its project?