ObsessionDB retweeted
Unpopular opinion: your data warehouse/platform should not make money from your waste. Today, most of them do.
Consumption pricing means your vendor earns more when your queries or schema are suck. Some of them charge crazy multiples on the underlying infra. That is not a partnership; it feels like they are extracting from you.
Data warehouses and data platforms should be more aligned with customers:
1. Infra at cost. You see the real cloud bill, line by line.
2. One platform fee. No overages. No markup.
3. Run it in your cloud, on your hardware, or go managed. No difference in the price.
If we save you money, we should win too. If your bill goes up because you burned more compute, we don't extract extra margins. The old model doesn't make any sense to me.
Is this naive?
ObsessionDB retweeted
We just added Jev support to ObsessionDB/ClickHouse.
The interesting part isn’t just “LLM in SQL”, it’s that Jev is fast enough to make semantic queries feel like part of the database workflow.
You can analyze AI agent sessions on the go!
aiFilter(session, 'was the user frustrated, map('model','jev-1.13.0'))
or score frustration, success, intent, exposed credentials, etc.
At write time: turn meaning into columns.
At read time: ask new questions you never instrumented.
~50 rows/request, ~300ms in our current setup.
Feels like a new primitive for AI product telemetry.
ObsessionDB retweeted
Just waiting for the PR getting merged to finally see ObsessionDB on benchmark.clickhouse.com. Spoiler: It's fast
ObsessionDB retweeted
Three replicas of a ClickHouse® table mean three full copies of the same data.
You are paying your storage bill three times and calling it durability.
The replication tax nobody names:
ObsessionDB retweeted
What's your biggest pain when operating a ClickHouse® database?
If your first thought is handling heavy data operations, keep reading.
ObsessionDB retweeted
Everyone building an MCP server is wrapping their REST API as 40 tools.
We shipped one for our ClickHouse database and deliberately gave the agent ~10. Most of the power lives in a single tool.
Here's the call we made, and why.
ObsessionDB retweeted
Your data warehouse provider doesn't want your agent costs to go down.
Consumption billing means they make more money every time an agent scans your data. The thing wrecking your margins is the thing they bill on.
In the agent era, the edge goes to whoever decoupled cost from query volume. That isn't the infra you're on today.
ObsessionDB retweeted
We are moving all our public datasets from BigQuery to Clickhouse®.
Clickhouse will allow our customers to build endpoints right from the data warehouse and consume data at a cost of an order of magnitude lower.
If you consume our public data sets, reach out so we can help you with the migration!
ObsessionDB retweeted
Agents don't think twice before running a query. They just run it.
On BigQuery or Snowflake, that's an expensive habit.
If your warehouse isn't fast and cheap by design, agentic workflows will punish you at scale.
Everyone should move to ClickHouse.












