Why is Snowflake so expensive
blog.devgenius.io
Why is Snowflake so expensive
1–10 of 217 posts
Re: Why is Snowflake so expensive
#2You would think they would be saving (and charging the customer!) a bundle not enforcing constraints on their tables.
I’d be very interested to hear the Snowflake side of this decision, but to the customer it’s simply unforgivable to have cosmetic constraints on a database.
Re: Why is Snowflake so expensive
#3[deleted]
Re: Why is Snowflake so expensive
#4No post body was provided.
Re: Why is Snowflake so expensive
#5Quoted post unavailable.
It makes perfect sense if you know that Snowflake is a product/company. It just needs to be capitalized (and the trailing question mark restored).
Re: Why is Snowflake so expensive
#6The monthly bill does make me wince, but Snowflake of course includes all server and compute costs, no installation, initial configuration or upgrades etc. It’s genuine SaaS.
It’s also very simple to manage and optimise so less DBA or DevOps type manpower.
Then of course you can perfectly right size your instances and pay by the second for compute and by the byte for storage.
Expensive, but lower TCO than alternate approaches I suspect.
Re: Why is Snowflake so expensive
#7Great article. On the surface, it's about Snowflake. At a deeper level, the article is about the perverse incentives motivating SaaS businesses to do seemingly dumb, inefficient things and avoid seemingly obvious optimizations by default.
Many SaaS businesses are perfectly happy to let customers shoot themselves in the foot if it generates more revenue. The BigQuery example (presently, by default, `select * from table limit 10` obediently scans the entire table at your expense!) is spot-on.
As the article so well puts it, every SaaS company has a vested financial interest "to leave optimization gremlins in."
Re: Why is Snowflake so expensive
#8No post body was provided.
Re: Why is Snowflake so expensive
#9You would think they would be saving (and charging the customer!) a bundle not enforcing constraints on their tables. I’d be very interested to hear the Snowflake side of this decision, but to the customer it’s simply unforgivable to have cosmetic constraints on a database.
Do you have any data on the pricing of distributed databases that do support proper foreign key constraints? And how it stacks against Snowflake pricing?