4 ms·

Snowflake is becoming the Juicero of data.

markus_zhang 1y ago
As a DE, I have an unpopular disdain of Snowflake because it trivalize a lot of stuffs. I think I'm going to switch to OLTP given the chance.
- gigatexal 1y ago
  Can you go into more depth on this?
- FridgeSeal 1y ago
  Right there with you. Developed my disdain after having to put up with the incredibly shitty behaviour from the sales and account teams a few years ago. Sure they had some novelty years ago, but everyone and their dog has disaggregated compute these days, and all their other “feature” just feel like enterprise money extraction that they’ve acquihired in. Expensive, slow, and painful.
  - smohare 1y ago
    [dead]
- 9283409232 1y ago
  If you're using Snowflake as an OLTP you're looking at the wrong technology anyway.
9283409232 1y ago
If you can afford it, I have a hard time coming up with reasons to not use Snowflake.
- skeeter2020 1y ago
  One good reason is that a huge population of companies just don't have enough data to justify Snowflake. We sell a product built on it, and I wish we'd had DuckDB 3-4 years ago; it's perfect for 95%+ of our clients
  - 9283409232 1y ago
    I think DuckDB is great but I don't think it is necessarily playing the same game as Snowflake. A lot of people want the serverless option and DuckDB is not that.
    - mrbungie 1y ago
      DuckDB on a lambda/serverless python function wrapper or in WASM (for client-side workloads) is as stateless and serverless as you can get. In that case BigQuery is more managed than both, PAYG for analytical queries without thinking about compute nor clusters whatsoever.
      - deleted 1y ago
        [deleted]
      - 9283409232 1y ago
        BigQuery is more expensive than Snowflake though. You might as well just do Motherduck which would be cheaper than BQ but let you pull data from S3 which is cheaper than Snowflake storage.
- ziml77 1y ago
  Just for the data sharing feature alone it's worth using. It's so damn easy to onboard and maintain data sources when they have a Snowflake share. You don't have to worry each day about loading processes randomly failing and you don't have to write any custom logic to hit APIs and properly flatten and merge responses into the database.

As a DE, I have an unpopular disdain of Snowflake because it trivalize a lot of stuffs. I think I'm going to switch to OLTP given the chance.

gigatexal 1y ago
Can you go into more depth on this?
FridgeSeal 1y ago
Right there with you. Developed my disdain after having to put up with the incredibly shitty behaviour from the sales and account teams a few years ago. Sure they had some novelty years ago, but everyone and their dog has disaggregated compute these days, and all their other “feature” just feel like enterprise money extraction that they’ve acquihired in. Expensive, slow, and painful.
- smohare 1y ago
  [dead]
9283409232 1y ago
If you're using Snowflake as an OLTP you're looking at the wrong technology anyway.

9283409232 1y ago

If you can afford it, I have a hard time coming up with reasons to not use Snowflake.

skeeter2020 1y ago
One good reason is that a huge population of companies just don't have enough data to justify Snowflake. We sell a product built on it, and I wish we'd had DuckDB 3-4 years ago; it's perfect for 95%+ of our clients
- 9283409232 1y ago
  I think DuckDB is great but I don't think it is necessarily playing the same game as Snowflake. A lot of people want the serverless option and DuckDB is not that.
  - mrbungie 1y ago
    DuckDB on a lambda/serverless python function wrapper or in WASM (for client-side workloads) is as stateless and serverless as you can get. In that case BigQuery is more managed than both, PAYG for analytical queries without thinking about compute nor clusters whatsoever.
    - deleted 1y ago
      [deleted]
    - 9283409232 1y ago
      BigQuery is more expensive than Snowflake though. You might as well just do Motherduck which would be cheaper than BQ but let you pull data from S3 which is cheaper than Snowflake storage.
ziml77 1y ago
Just for the data sharing feature alone it's worth using. It's so damn easy to onboard and maintain data sources when they have a Snowflake share. You don't have to worry each day about loading processes randomly failing and you don't have to write any custom logic to hit APIs and properly flatten and merge responses into the database.