Earlier quoted context omitted.
Databricks is way more than hadoop or spark. A great analogy - Spark is a great engine but you need to design and build all of the other subsystems. Databricks is an F1 car - everything is built out. You get in and drive - FAST.
> Databricks is an F1 car F1 cars really unreliable and need a lot of engineers to keep running, are very expensive, and completely impractical in normal use. They are fast but only on very specific roads, they couldn't survive on normal roads. What do you know, you might be right! :D
Databricks response to Snowflake's accusation of lacking integrity
101–110 of 168 posts
Re: Databricks response to Snowflake's accusation of lacking integrity
#102Data Wars: Snowflake vs Databricks (0 - 2)?
Snowflake has way more revenue, is worth 3 times more than Databricks and is growing faster. I'd say Snowflake is still in the lead. Plus, just look at Snowflake's customer list. It's a "who's who", Databricks is a "Who's that?".
Atlassian? Adobe? ExxonMobil? PagerDuty? McAfee? HSBC? Starbucks? AstraZeneca? GlaxoSmithKline? Comcast? FINRA? Regeneron? Riot Games? Nielsen? HP? Conde Nast? Viacom? McGraw-Hill? Cisco? NBCUniversal?
Hopefully they can scale to the enterprise soon.
Re: Databricks response to Snowflake's accusation of lacking integrity
#103Ive been following this and it’s kind of embarrassing to watch. I love working with Databricks and Snowflake. They both knock it out of the park for their respective use case. They’re amazing products. It makes no sense to fall out about this though. For a 100TB dataset with a funky calculation, Spark will trounce Snowflake. For a 1 row dataset, Snowflake will return before the spark job has been serialised.
Also what kind of queries are we talking about?
Re: Databricks response to Snowflake's accusation of lacking integrity
#104I've used both products in production. Both are good++. The blog wars seem extremely ridiculous to me. I don't recall ever choosing one over another based on how fast it runs on some imaginary arbitrary dataset.
Its not ridiculous at all. This is the coming of age for a brand new data architecture. One of the biggest FUDs for a data lake architecture is performance - and this benchmark should put that concern to rest.
Re: Databricks response to Snowflake's accusation of lacking integrity
#105Earlier quoted context omitted.
Databricks isn't open source, as they keep hold of all the IP that makes it much better than OS Spark. Whether you buy Snowflake or Databricks, you're buying proprietary software.
This is very true. They make the lowest common denominator parts "open source" but control all of the commits. Also the query engine used for this benchmark is proprietary, closed source (Photon)
But with Snowflake, the data never comes out. Can't use Spark/Trino/Flink... on data in SF.
Re: Databricks response to Snowflake's accusation of lacking integrity
#106Earlier quoted context omitted.
Please read up on Lakehouse. Data Lake + Merge support + DW performance is now possible. That is the game changer.
It'll take a few more years until these companies fixed all the bugs and address all the scalability issues. As of today, these companies are not good enough to take on the Data Warehouse part.
Re: Databricks response to Snowflake's accusation of lacking integrity
#107Earlier quoted context omitted.
This is very true. They make the lowest common denominator parts "open source" but control all of the commits. Also the query engine used for this benchmark is proprietary, closed source (Photon)
The 'open' here refers to the data. Delta lake can be read/written by multiple open source engines, not just Spark. Not to mention, if you want you can use Databricks with Parquet, though the experience won't be as good. But with Snowflake, the data never comes out. Can't use Spark/Trino/Flink... on data in SF.
This is the problem. Both Snowflake and Databricks are spreading FUD and otherwise smart people are falling for it.
Re: Databricks response to Snowflake's accusation of lacking integrity
#108What I find hilarious is that companies argue who can query 100 TB faster and try to sell this to people. I've been on the receiving end of offers by both of the companies in question and used both platforms (and sadly migrated some data jobs to them). While they can crunch large datasets, they are laughably slow for the datasets most people have. So while I did propose we use these solutions for our big-ish data pro…
Re: Databricks response to Snowflake's accusation of lacking integrity
#109Earlier quoted context omitted.
This is very true. They make the lowest common denominator parts "open source" but control all of the commits. Also the query engine used for this benchmark is proprietary, closed source (Photon)
The 'open' here refers to the data. Delta lake can be read/written by multiple open source engines, not just Spark. Not to mention, if you want you can use Databricks with Parquet, though the experience won't be as good. But with Snowflake, the data never comes out. Can't use Spark/Trino/Flink... on data in SF.
Re: Databricks response to Snowflake's accusation of lacking integrity
#110Earlier quoted context omitted.
This is very true. They make the lowest common denominator parts "open source" but control all of the commits. Also the query engine used for this benchmark is proprietary, closed source (Photon)
The 'open' here refers to the data. Delta lake can be read/written by multiple open source engines, not just Spark. Not to mention, if you want you can use Databricks with Parquet, though the experience won't be as good. But with Snowflake, the data never comes out. Can't use Spark/Trino/Flink... on data in SF.