Snowflake has skyrocketed in popularity over the past 5 years and firmly planted itself at the center of many companies' data stacks. Snowflake came into existence in 2012 with a unique architecture, described in their seminal white paper as "the elastic data warehouse". Rather than have compute and storage coupled on the same machine like their competitors did, they proposed a new design that took advantage of the near-infinite resources available in cloud computing platforms like Amazon Web Services (AWS). In this post, we'll dive into the three layers of Snowflake's data warehouse architecture: cloud services, compute and storage.
I submit my own materials regularly without disclosing. It's awkward to post after to submitting. Articles are either interesting or they are not. Readers on HN are pretty discerning and can make up their own minds.
Your article is a nice intro for people who don't understand how Snowflake works. Thank you for the submission. I'll be interested to see what you are doing.
6 comments
[ 3.1 ms ] story [ 23.0 ms ] threadSubmitter is also the author and founder of select.dev, a service selling Snowflake optimization.
Your article is a nice intro for people who don't understand how Snowflake works. Thank you for the submission. I'll be interested to see what you are doing.
These are not original to SF. COW snapshot cloning has been around for decades, and eg Vertica has had a copy_table function since IDK how long.
Time travel was in V1 of Vertica, and a quick search shows the same feature in DB2 and other platforms.