Katz: ClickHouse handled 30 billion daily events when built at Yandex
Aaron Katz · Fireside Chat: Aaron Katz (Co-Founder & CEO, ClickHouse) with Matt Turck (Partner, FirstMark) · Nov 16, 2021 · at 5:16
Aaron Katz, Co-Founder and CEO of ClickHouse, discusses historical data volumes that drove the database's original development.
0:00 / 0:11exact quote · 12.0s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“When it was originally written inside Yandex, the data volumes that they were seeing were at the time, you know, some of the highest in the market, you know, let's say, thirty billion events per day.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Aaron Katz
SDR and CSM roles often serve as a crutch, says Aaron Katz
“In my experience, it can often, both of those functions can be a crutch for a broader issue inside of the company.”
ClickHouse sees demand to migrate workloads off Snowflake, BigQuery, and Redshift
“In the cloud data warehouse market, to answer your question specifically around Snowflake, we do see demand for customers to migrate off of technologies like BigQuery and Redshift, and Snowflake either for Cost or performance or both.”
Aaron Katz: Cradle-to-grave sales reps boost efficiency and customer retention
“If you can enable your direct sales team to kind of handle a lead from cradle to grave I think you're going to drive efficiency as part of your sales organization. I think you're going to improve your customers buying experience and you're going to have higher…”
Katz recommends Datadog for hosted APM over stitching custom solutions
“If you are looking to deploy a hosted APM solution, and you asked me objectively, my recommendation, I'd say use Datadog. I'd say that the product, the maturity, the experience is, is considerably better than trying to stitch together something using ClickHous…”
Snowflake was not engineered for low-latency, high-concurrency workloads, says Katz
“Snowflake is a columnar, a data store with the separation of compute and storage like we have with our cloud service. But I don't believe that it was originally engineered to power these extremely low latency, high concurrent analytical workloads.”