The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused.
My core question is why would I use this instead of duckdb and writing SQL as God intended[2]?
Comments
The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused.
My core question is why would I use this instead of duckdb and writing SQL as God intended[2]?
---
[1] A clear indication of AI generation
[2] This is a joke.
FWIW I liked your joke :D
I think God did intend SQL for us. There is no going back. It's too deeply intertwined.
[2] duckdb indexes suck
Remember duckdb is for OLAP, not OLTP!
olap doesn't mean no indexes. Prev gen olap (cubes, star schemas) were index heavy, you can't achieve subsecond analytics without indexes.