Databricks, every mention
28 scenes (2025), the whole family · ← back to Databricks
every year 2025 anyone Matt Turck 107Ali Ghodsi 16Ben Rogojan (Seattle Data Guy) 12Tomasz Tunguz 10Mike Palmer 7Justin Borgman 5Florian Douetteau 5Ion Stoica 4Alex Dean 4Jack Berkowitz 3
Verbatim, from the transcripts: the passages where Databricks comes up
Rewriting Success: What InfluxDB 3.0 Teaches About Scaling—and Scrapping—Your Core Tech
- ▶ 10:37 Evan Kaplan And I, listening to Mike's talk, well, we still use Excel from 1985, so, so there was a little bit of humble pie for us to eat, because it was pretty clear that the language, and this is, this is right around the time of the, we really… 2 times in the scene
- ▶ 16:33 Matt Turck Uh, so that, and then, uh, for the sort of Databricks, Lakehouse, uh, iceberg kind of world, um, so first of all, like, I saw that you guys coined your own acronym. 2 times in the scene
- ▶ 20:22 Evan Kaplan And we're now moving it to Snowflake or Databricks and do it.
Dashboards Are Dead: Sigma’s BI Revolution for Trillion-Row Data
- ▶ 0:26 Matt Turck Now, Sigma is reinventing BI by enabling anyone with spreadsheet skills to analyze massive amounts of data in Snowflake or Databricks in seconds.
- ▶ 11:28 Mike Palmer So for example, uh, in our world, we needed a Snowflake, a Databricks, a BigQuery, a Redshift,
- ▶ 16:37 Mike Palmer So one of the things that changed, obviously, with the Databricks and the Snowflakes and the Big Queries and so forth is that the data volumes got huge. 4 times in the scene
- ▶ 31:07 Mike Palmer Uh, but I do think that the other ones, like the Databricks of the world, the Snowflakes of the world, Google made an attempt at this, but I think that Google, I think Google missed the zeitgeist.
- ▶ 34:43 Mike Palmer Snowflake and Databricks are frustrated by the cost and complexity of moving data into their warehouses.
Box’s Big AI Leap: Aaron Levie on Agents & the Future of Work
- ▶ 46:16 Matt Turck And we were talking about Snowflake a minute ago, and they did their, you know, Arctic model, and, you know, Databricks did, like, PJRX.
Snowflake CEO on Winning the AI Arms Race
- ▶ 19:57 Sridhar Ramaswamy It's an Apache project with a set of contributors that come from many places, from Netflix, from Snowflake, from Databricks, from AWS, but it is vendor neutral.
- ▶ 1:08:35 Matt Turck Uh, regardless of space seems to be hitting up, or Confluent is cozying up with, um, Databricks.
- ▶ 1:19:45 Matt Turck It sounds like Databricks sort of did the same thing, right? 2 times in the scene
Trino, Iceberg and the Battle for the Lakehouse | Justin Borgman, CEO, Starburst
- ▶ 4:54 Justin Borgman On the analytical side, you'd think of, uh, Teradata, Snowflake, Databricks, and Starburst.
- ▶ 17:37 Matt Turck Uh, but in the cloud data warehouses, obviously you have, uh, Snowflake, uh, Redshift, uh, Google BigQuery, uh, in the world of DataLex, uh, who, originally Hadoop, at some point, early Databricks. 2 times in the scene
- ▶ 19:36 Justin Borgman You have a couple giant players in Databricks and Snowflake that are now looking for adjacent markets to continue to grow their TAM and justify their valuations and drive their revenue into the future.
- ▶ 20:14 Justin Borgman Number one, we're one of the only hybrid players, so Databricks and Snowflake are cloud only, so if you happen to have data on-prem, uh, we're pretty much your only bet, and you know, it just so happens that that turns out to be most of… 2 times in the scene
- ▶ 41:30 Justin Borgman Um, and actually what's interesting is that first architecture was actually fairly similar to Databricks' architecture
- ▶ 47:39 Matt Turck Was that the acquisition of Tabular by Databricks? 8 times in the scene
Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
- ▶ 0:46 Ben Rogojan (Seattle Data Guy) Databricks had bought Tabular.
- ▶ 6:13 Ben Rogojan (Seattle Data Guy) Uh, yesterday I accidentally, like when I put out my newsletter, uh, I accidentally said that Databricks had bought tabular, uh, not tabular. 2 times in the scene
- ▶ 14:18 Ben Rogojan (Seattle Data Guy) One team's gonna be using Databricks.
- ▶ 31:23 Ben Rogojan (Seattle Data Guy) I don't know if you've seen his content, but he does a lot of Databricks content, and we were kind of going through and testing out Databricks Genie.
- ▶ 31:23 Ben Rogojan (Seattle Data Guy) I don't know if you've seen his content, but he does a lot of Databricks content, and we were kind of going through and testing out Databricks Genie. 2 times in the scene
- ▶ 37:24 Matt Turck Do you view, uh, you know, the hyperscaler, um, you know, whatever Microsoft Fabric or being able to provide, or Databricks trying to provide all the things for all people? 9 times in the scene
- ▶ 42:05 Matt Turck You know, that, uh, I saw you, you, uh, write in one of your, one of your posts, uh, which I thought was super interesting, especially, like, in contrast to, like, this whole, you know, titanic fight between Databricks and, and, and… 2 times in the scene
- ▶ 47:55 Ben Rogojan (Seattle Data Guy) Do we need a Databricks?
- ▶ 49:14 Ben Rogojan (Seattle Data Guy) Similar with BigQuery, I think Databricks makes sense to me still more from an ML standpoint. 3 times in the scene
- ▶ 50:48 Ben Rogojan (Seattle Data Guy) Um, so I think in those places, you're going to see people pick other tools, or maybe somehow have five different instances of, uh, iceberg, uh, or, you know, maybe they've, one's using Databricks, one's using Snowflake, one's using AWS,…