May 15, 2026
SQL, but make it drama
A SQL-Inspired Query Language Designed for Event Sourcing (2025)
New event search tool drops, and the comments instantly turn into a naming fight
TLDR: EventQL is a new language meant to make searching event histories easier by using a style that feels familiar to database users. Commenters immediately shifted the spotlight to two things: a possible name clash with an older project, and whether this neat idea can actually fit into real-time systems people use every day.
A new tool called EventQL is pitching itself as the easier way to search through giant logs of app activity — basically a cleaner way to answer questions like “what happened?” and “when did it happen?” in systems that keep every change as a permanent record. The sales pitch is simple: make this stuff feel more like regular database searching, but built for streams of events instead of old-school tables. For people who build software this way, that’s a big deal, because digging through mountains of past actions can be painfully slow and confusing.
But in classic internet fashion, the real action was in the replies. One of the first commenters barged in with a record-scratch moment: uh, isn’t there already something called EventQL? They even dropped a GitHub link and a presentation link like a courtroom exhibit, instantly turning a dry product post into a mini identity crisis. That sparked the biggest vibe in the thread: less “wow, cool syntax” and more “boys, we may already have a naming situation.”
Then came the thoughtful skeptic energy. Another commenter basically said: looks smart, but how does this actually plug into live, reactive systems? In plain English: nice query language, but can it do more than look pretty in examples? The humor here is subtle but real — one camp is impressed by the polished, familiar style, while the other is already asking the dreaded follow-up: okay, but does it work in the messy real world?
Key Points
- •The article says querying append-only, immutable event streams is challenging because events contain metadata, hierarchical subjects, and nested payloads that require specialized filtering and transformation.
- •EventQL is presented as a SQL-inspired query language originally designed for EventSourcingDB by The Native Web.
- •EventQL exposes event properties such as type, subject, id, time, and payload fields as first-class query elements.
- •The article highlights subject hierarchies as a way to scope queries to aggregates and support efficient subject-based indexing.
- •EventQL requires explicit projection with PROJECT INTO and is described as being designed to encourage index-friendly queries across event type, subject, timestamp, and selected data fields.