3 ms·
I've already thought of the follow-up to this article, 'Querying a billion rows on a $XX budget.' Let me give you my answer directly: switch from Snowflake to S
by HermitX 3y ago
I've already thought of the follow-up to this article, 'Querying a billion rows on a $XX budget.' Let me give you my answer directly: switch from Snowflake to StarRocks. It's an open-source project under the Linux Foundation, with speed that's more than adequate, especially for queries involving multiple tables. If you're interested, you might want to check it out, https://medium.com/starrocks-engineering/how-to-reduce-snowflake-costs-by-80-deb87aa69bc5 https://medium.com/starrocks-engineering/how-to-reduce-snowf....
- ako 3y agoStarrocks sounds too good to be true, what are the cons?
- 392 3y agoHard to set up in Kubernetes. Seems to want you to know too many specifics for how to shard your db ahead of time. Don't remember how it handles schema evolution. I settled for Databend because it just worked easy and fast with nothing more than table definitions.
- hodgesrm 3y agoDo you have a connection with StarRocks?
- HermitX 3y agoWhat do you want? You can connect with the StarRocks eng team on the slack channel. https://join.slack.com/t/starrocks/shared_invite/zt-z5zxqr0k-U5lrTVlgypRIV8RbnCIAzg https://join.slack.com/t/starrocks/shared_invite/zt-z5zxqr0k...