Both are great products but it depends on the scale of what you’re doing and how much engineering you want to do. Also, if your developers aren’t as expensive as in the US then cost savings make more sense. In terms of ease of use Snowflake has the advantage until you need something that doesn’t fit their idea of simple and you’re left on your own to figure it out. When you go off the rails you see the land is bare whereas in Databricks it’s full of tricks you can pull off to solve your problem. In my choice depending on the level of engineering you want to do it would be Snowflake -> Databricks -> do it yourself on top of open source and even create your own like Netflix, Airbnb, Uber do for example. I like Databricks as a good middle ground between too much simplicity and too much complexity.
Not surprised at all that Databricks would be giving overly discounted DBU rates to win workloads from Snowflake. GCP has been doing this for years to win workloads from AWS & Azure, then their customers get their eyes ripped out when the renewal comes along. Excited to see Databricks start working with Iceberg - I think they've realized that calling Delta "open source" and then completely controlling the direction of the project has soured some customers. Iceberg will win out as the most commonly-adopted open source table format and it will force Snowflake and Databricks to truly compete to be the better engine rather than competing for headlines
@@peterkingz2403 with Delta I agree that it was mostly a marketing move with outsourcing it, but not sure Iceberg will have such a big impact to make them compete one to one. I think they’ll eventually steer Iceberg as well
@@distantsight I am by default as that’s my day to day but in these videos I try to keep some balance. But I always say they are both relevant for different use cases and some crossover. Hope you enjoyed it still
Both are great products but it depends on the scale of what you’re doing and how much engineering you want to do. Also, if your developers aren’t as expensive as in the US then cost savings make more sense.
In terms of ease of use Snowflake has the advantage until you need something that doesn’t fit their idea of simple and you’re left on your own to figure it out. When you go off the rails you see the land is bare whereas in Databricks it’s full of tricks you can pull off to solve your problem.
In my choice depending on the level of engineering you want to do it would be Snowflake -> Databricks -> do it yourself on top of open source and even create your own like Netflix, Airbnb, Uber do for example. I like Databricks as a good middle ground between too much simplicity and too much complexity.
@@alexischicoine2072 completely agree with you, good points
Not surprised at all that Databricks would be giving overly discounted DBU rates to win workloads from Snowflake. GCP has been doing this for years to win workloads from AWS & Azure, then their customers get their eyes ripped out when the renewal comes along. Excited to see Databricks start working with Iceberg - I think they've realized that calling Delta "open source" and then completely controlling the direction of the project has soured some customers. Iceberg will win out as the most commonly-adopted open source table format and it will force Snowflake and Databricks to truly compete to be the better engine rather than competing for headlines
@@peterkingz2403 with Delta I agree that it was mostly a marketing move with outsourcing it, but not sure Iceberg will have such a big impact to make them compete one to one. I think they’ll eventually steer Iceberg as well
You are so biased towards Databricks we can not take you seriously
@@distantsight I am by default as that’s my day to day but in these videos I try to keep some balance. But I always say they are both relevant for different use cases and some crossover. Hope you enjoyed it still
6:38😂