Skip to content

2025 in Review: A Year of Events

On May 5th, 2025, we shipped EventSourcingDB 1.0. After years of building, learning, and refining, we finally had a product we were proud to put in front of the world. That moment marked the beginning of something we had dreamed about for a long time. Now, as the year draws to a close, it's time to look back at what has happened since then – and to say thank you.

From 1.0 to 1.2

When we released 1.0 in May, we knew it was just the starting point. The foundation was solid, but we had a long list of ideas waiting to be built. Over the following months, we shipped two major releases that brought significant new capabilities to EventSourcingDB.

Version 1.1 arrived in September. It introduced Dynamic Consistency Boundaries, giving teams more control over how consistency is enforced across aggregates. We added EventQL Preconditions with the isEventQlQueryTrue check, enabling fine-grained query-based validation before writes. And we shipped Event Signatures using Ed25519, allowing optional cryptographic signing for stronger integrity guarantees. These features came directly from conversations with early adopters who were pushing EventSourcingDB in production.

Version 1.2 followed in November. We added the isSubjectPopulated precondition to prevent accidental writes to empty subjects. We made signature and hash fields accessible in EventQL, so teams in audit-heavy environments can validate integrity directly in queries. We translated the management UI into German and added a language switcher. And we expanded the documentation with new guides and resources.

Each release reflected what we heard from the community. Your feedback shaped what we built – and the numbers show that more and more people are exploring what EventSourcingDB can do.

Growth in Numbers

Since May, we've seen steady growth across the ecosystem:

Since launching the blog in October, we've published 22 articles (including this one) covering everything from architectural fundamentals to technical deep dives. These numbers matter to us not as vanity metrics, but because they represent real people exploring event sourcing and giving EventSourcingDB a chance.

A Growing Ecosystem

But EventSourcingDB was never meant to exist in isolation. From the beginning, we wanted to build a foundation that others could build upon – and this year, that vision started becoming reality.

We launched several companion sites to help developers discover event-driven patterns:

  • cqrs.com – a practical introduction to CQRS and event-driven architecture
  • eventsourcing.ai – exploring the intersection of event sourcing and artificial intelligence
  • eventsourcingdatabase.com – a guide to choosing the right event sourcing database

We now offer client SDKs in six languages: .NET, Go, JavaScript/TypeScript, PHP, Python, and Rust. Teams can integrate EventSourcingDB into their existing stacks without friction.

And in October, our friends at Digital Frontiers released OpenCQRS 1.0 – a production-ready CQRS and Event Sourcing framework for the JVM with native EventSourcingDB integration. This was a milestone not just for them, but for the entire ecosystem. You can read more about it in Celebrating OpenCQRS 1.0.

Meeting the Community

Beyond code and downloads, one of the most rewarding parts of this year was meeting so many of you in person. At KanDDDinsky 2025 and the Software Architecture Gathering in Berlin, we had countless conversations about CQRS, Event Sourcing, and the challenges of building event-driven systems.

At the Software Architecture Gathering, around 120 people joined my talk on why CRUD falls short when modeling real-world processes. The discussions continued long after the session ended, and many attendees shared similar frustrations with traditional approaches in their own projects.

We are deeply grateful for every conversation, every question, and every piece of feedback. These exchanges aren't just nice to have – they directly shape what we build and how we think about the product.

Highlights From the Blog

Many of those conversations inspired us to write. When we launched the blog in October, we wanted to share more than just release notes – we wanted to tell stories, explain ideas, and give the community deeper insights into event sourcing and EventSourcingDB. Here are four highlights from the past months:

Ten Years, One Goal tells the story behind EventSourcingDB – from our first encounter with event sourcing over a decade ago, through the lessons learned building wolkenkit, to where we are today. It's a personal look at the journey that led us here.

Proving Without Revealing: Merkle Trees is a technical deep dive into how cryptographic data structures enable integrity verification without exposing underlying data. It explains one of the building blocks behind EventSourcingDB's tamper-evidence capabilities.

Event-Driven Data Science: EventSourcingDB Meets Python and Pandas explores how event sourcing provides richer data for analysis than traditional CRUD systems. It demonstrates practical patterns for extracting insights from event streams using Python.

... And Then the Wolf DELETED Grandma is the written version of my talk at the Software Architecture Gathering. It uses the story of Little Red Riding Hood to explain why CRUD breaks when modeling real-world processes – and how Event Sourcing preserves the full story.

EventSourcingDB Cloud

While we've been busy with releases and content, we've also been working on something else. Running EventSourcingDB yourself is straightforward, but many teams want a fully managed option. That's why we've been working on EventSourcingDB Cloud. We're currently running a private beta and onboarding participants in waves to ensure a smooth experience.

If you're interested in joining the beta and getting a managed EventSourcingDB instance without the operational overhead, reach out to us at hello@thenativeweb.io.

Thank You

But more than anything else, as this year comes to an end, we want to express our deepest gratitude.

Thank you to our customers who trusted EventSourcingDB early on, put it into production, and challenged us with real-world requirements. Your confidence in what we're building means everything.

Thank you to the community – everyone who filed issues, contributed ideas, asked questions, and helped spread the word. Your engagement pushes us to keep improving.

Thank you to our partners, especially the team at Digital Frontiers, for believing in the vision and building alongside us.

Building a database is a long journey, and we couldn't do it without all of you.

See You in 2026

With this post, we're closing the blog for the year. We'll be back in January after the holidays, ready to share more stories, announcements, and insights.

Until then: Merry Christmas and a wonderful start to 2026. Take some time to rest, reflect, and enjoy the people who matter most to you.

Thank you for being part of this year of events. We can't wait to see what the next one brings.