5/13/2026 at 7:02:52 PM
by goloroden
5/16/2026 at 12:33:40 AM
Looks well thought out, but what are the mechanics of plugging this into reactive workflows? I always thought a nice event sourcing query language would evolve along the thoughts in https://picolabs.atlassian.net/wiki/spaces/docs/pages/118989...by cgio
5/16/2026 at 12:26:19 AM
There is already a database named EventQL: https://github.com/eventql/eventql I covered it in my presentation: https://presentations.clickhouse.com/2018-unknown_developers...by zX41ZdbW
5/16/2026 at 11:12:14 AM
Having built two production, scaled evented systems over the last decade, I don’t see the need for this. Properly designed events flatten to a table schema in a regular DB quite easily. Tools like Trino/Presto and therefore Athena, let you deep query on a JSON field, as well (e.g. against a Parquet-based event store on block storage), so if you use a standard envelope, the bodies are all still available without having to provide the schema for every event. This works to quite huge amounts of data given that you do rollups and/or snapshots.by relistan