patriceckhart

6 ms·

1. 61.▲
   by patriceckhart 1y ago

   Not open source, but we're planning to open things up with Genesis DB CE - a free, fully usable community edition: https://www.genesisdb.io/blog/posts/2025-09-25/genesis-db-1-...
2. 62.▲
   by patriceckhart 1y ago

   I appreciate your remarks and the perspective, that's valuable feedback. I'll think about adjusting it to make the message clearer.
3. 63.▲
   by patriceckhart 1y ago

   Thank you for your comment! I think it's actually your very first one on Hacker News, or am I mistaken? If you run into bugs and want to share them, please just open an issue in the GitRepo's, or send us a message, ... Genesis DB
4. 64.▲
   by patriceckhart 1y ago

   It's a playful metaphor. We meant that the logs are thorough, reflective, and give you insights. They help you understand your system and its processes. No worries, you won't end up contemplating the meaning of life, unless you re
5. 65.▲
   by patriceckhart 1y ago

   I understand. Honestly, it was never my intention to get rich with this project. Covering a bit of the development time, servers, and so on would already be nice. Since Genesis DB doesn't limit the number of instances you can run, I wo
6. 66.▲
   by patriceckhart 1y ago

   That's a valid question. At the very least, disclosing the libraries being used might even be mandatory. I'll check on that asap and add it to the documentation.
7. 67.▲
   by patriceckhart 1y ago

   TimescaleDB looks great and is built on top of Postgres. Genesis DB, in contrast, is a straightforward (if not simpler) event store that manages data differently than Postgres. That said, TimescaleDB is definitely worth a look.
8. 68.▲
   by patriceckhart 1y ago

   Not at the moment, but I'm considering a one-time payment option since people generally dislike subscriptions.
9. 69.▲
   by patriceckhart 1y ago

   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.
10. 70.▲
    by patriceckhart 1y ago

    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.
11. 71.▲
    by patriceckhart 1y ago

    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 w
12. 72.▲
    by patriceckhart 1y ago

    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&
13. 73.▲
    by patriceckhart 1y ago

    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 PH
14. 74.▲
    by patriceckhart 1y ago

    Thanks a lot! That means a lot. Simplicity + real-world workflows is exactly what I wanted to nail.
15. 75.▲
    I Built an Event-Sourcing Database Engine: Meet Genesis DB(genesisdb.io)

    45 points by patriceckhart 1y ago|40 comments
16. 76.▲
    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 deve