DuckDB should give you everything with regards to DevEx that you seem to be needing. You're not specifying what volume we're talking about here, but I'd be sur

DuckDB should give you everything with regards to DevEx that you seem to be needing. You're not specifying what volume we're talking about here, but I'd be surprised if you can't go a long way with DuckDB. Ultimately the bottleneck for latency in a non-big data scenario will be memory? You can run it in a browser: https://github.com/duckdb/duckdb-wasm https://github.com/duckdb/duckdb-wasm DuckDB's docs and blog are full of great content with regards to optimizing: How to tune workloads: https://duckdb.org/docs/guides/performancehow_to_tune_workloads.html https://duckdb.org/docs/guides/performancehow_to_tune_worklo... Performance guide: https://duckdb.org/docs/guides/performance/overview.html https://duckdb.org/docs/guides/performance/overview.html Optimizers in DuckDB: https://duckdb.org/2024/11/14/optimizers.html https://duckdb.org/2024/11/14/optimizers.html I'm sure there is more. If I were in your shoes, even if you don't settle on DuckDB, it would be my go to benchmark due to ease of use and unoptimized speed. Anything else out there like chDB (Clickhouse) or Apache Datafusion should be worth the effort. For a detailed benchmark of DuckDB vs. Clickhouse for an orientation, see: https://bicortex.com/duckdb-vs-clickhouse-performance-comparison-for-structured-data-serialization-and-in-memory-tpc-ds-queries-execution/ https://bicortex.com/duckdb-vs-clickhouse-performance-compar...