|
|
|
|
|
by bonobocop
237 days ago
|
|
The durability and transformation reasons are definitely more compelling, but the article doesn’t mention those reasons. It’s mainly focused on the insert batching which is why I was drawing attention to async_insert. I think it’s worth highlighting the incremental transformation that CH can do via the materialised views too. That can often replace the need for a full blown streaming transformation pipelines too. IMO, I think you can get a surprising distance with “just” a ClickHouse instance these days. I’d definitely be interested in articles that talk about where that threshold is no longer met! |
|