I don’t know? They have blog posts about it but I don’t know how much I’d trust them because their chosen replacement only lasted 5 months before the next replacement.
replyI think it was closer to what they need; it comes down to keeping TB of data on local SSD and having a query engine next to it. That takes persistent, shared CPU, caching, sharding, resource management, etc.
replyDuckdb is an interesting approach to resource management (all ephemeral), but TB's are TB's. I doubt it was finding data where it needed it.
Clickhouse seems slow at getting to the top end of scaling; it's stuck with the 99% of its userbase doing 1 GB queries. I'm hoping they put some of their money into it.
ClickHouse is fast OLAP. Just do Iceberg with Trino like a normal big data person. WTF?
replyDuckDB is now close to competitive with Trino. As the post shares, large distributed multi-tenant data systems require a ton of work no matter what technology you use, but as a huge DuckDB fan, I do have to agree that it is not an out of the box data warehouse, though check back in a year or so when DuckLake and DuckDB 2.0 have had time to mature a bit more for this use case.
replyUnless something has changed in the last year, a lot of teams have serious problems with stability.
replyPostHog has listed a lot of job openings in the last couple of years. I figured growth but maybe it’s turnover.
replyI am curious to learn more about those issues, anyone have shared their experience publicly? would love to read
replyRussian ties?
replyThat's where it started very long ago, but they are based out of the Netherlands mostly now.
replyhttps://clickhouse.com/blog/we-stand-with-ukraine
> We have no infrastructure, servers or people in Russia. The original engineering team successfully moved out of Russia and are now working in our Amsterdam office.
You can take the guy out of Russia.. :)
replyI kid but that's probably what people have a problem with.
No support for real S3 (zero copy replication) in the open source version.
reply