Anders

Anders

@dataders.bsky.social

DX @ dbt

1.6K followers812 following77 posts

this is the clearest case for Arrow that I've ever seen. I love that it's high-level but also doesn't shy away from details when it's important. this should be a #databs canon text imho. thanks @ianmcook.bsky.social !

Ian Cook@ian.columnar.tech

2025 is shaping up to be a breakout year for fast query result transfer with Apache Arrow. But what exactly makes it so fast? David Li, Matt Topol, and I break it down in this new blog post: arrow.apache.org/blog/2025/01...

imho, the most clear case Databricks has made in public on their Iceberg future post-Tabular acquisition. I agree with this vision of the future and it's nice to see DBRX sharing how they see themselves participating in it. worth clicking through the deck! #databs speakerdeck.com/databricksja...

speakerdeck.comIceberg Meetup Japan #1 : Iceberg and Databricks2月21日に開催されたIceberg Meetup #1で使用した資料になります。 DatabricksとIcebergを使用する際のカタログについてご紹介しています。
View full thread

10) So sick that a smallpond pipeline returns a LogicalPlan representing a DAG where each node is a distinct data processing task. Imagine if a dbt DAG resulted in a single logical plan that operates across multiple engines. and then they can optimize the plan before execution as well! 🤯🤯🤯

View full thread

9) Arrow is the unsung hero of this project (and arguably all innovation in data ecosystem). it's what enables: 1. all this interchangeability of query engines 2. (likely) using duckdb in a distributed environment in the first place

View full thread

6) Making smallpond 5 years ago would have been very difficult! but the emergence of lower-level, off-the-shelf components greatly accelerate the development time. Within the year, we'll to see this new paradigm catch on. Future examples will probably be using DataFusion not DuckDB.

7) TIRED: "big vs. small" & "distributed vs single-node" WIRED: tactical deployment of single-node query engines within distributed frameworks. another great example is Apache Comet which plugs DataFusion into Spark to accelerate single-node operations resulting in overal Spark performance speedups

View full thread

4) smallpond is a bespoke data processing framework using off-the-shelf, OSS components (ray, arrow, duckdb, polars). Why didn't they use {TOOL}? My guesses ❌ dbt: they wanted Python Dataframe API ❌ Airflow: not as close to metal as Ray ❌ pytorch or ray[data]: idk tbh

5) there's been previous discussion on DeepSeek's scrappiness and I think it shows here. They had a vision of what they wanted and rather than paying for software or forcing their vision into an existing tool, were able to ship exactly what they wanted

2) so cool to begin to see the data infra that supports training LLMs. Open weights is cool, and RAG makes sense, but as a former XGBooster turned "data engineer", seeing the data cleaning pipelines is what I've most wanted to see.

Anders reposted

Just finished watching the webinar on introducing SDF by dbt team. After seeing SDF in action, I have to admit that I am really looking forward to the future of dbt engine. I was wondering when dbt was going to bring in notable changes to the developer experience and this might be it. #databs

Look forward to these every year. Always love Andy's candor and insight on our little corner of the world. #databs

Andy Pavlo@andypavlo.bsky.social

Buckle up because we're banging into the new year with my annual retrospective of the last year in databases! Highlights include license change blowback, Databricks vs. Snowflake gangwar, @duckdb.org's shotgun weddings, and buying a quarterback to impress your lover: www.cs.cmu.edu/~pavlo/blog/...

my experience installing MSFT's ODBC driver on M-series macbook re-stokes my long-burning ire for Simba drivers and the company behind them. One might think MSFT is to blame for a less than medoicre database driver, but in a way they're victims here too, held captive by Simba. #databs

does anyone use the 1Password CLI? I feel it has potential to be very valuable for managing environment variables (esp for teams). but i'm hesitant to adopt bc it requires that every command you run consume the output of `op` developer.1password.com/docs/cli/get...

developer.1password.comGet started with 1Password CLI | 1Password DeveloperLearn how to install and sign in to 1Password CLI, then get started with commands and scripts to manage users, vaults, and items on the command line.

admittedly, I'm triggered by SFTP, but it's a good analogy! What if there was an SFTP where you didn't have to parse random-delimited text files, but could just query the tables inside?

Christian Minich@christianminich.com

@chris.blue writes a post-length version of “Iceberg on S3 is the new SFTP.” If you want to understand why SFTP is crucial to orgs, Chris has some great examples of how and why SFTP is used. All of his examples matched my experience in healthcare. #dataBS open.substack.com/pub/material...

4/ what about S3 Tables? aren't they then "bad" by not using the OSS API spec? 🤷 data teams are predominately on a single cloud, so what they need is a standard within a single provider. and, like @benesch.bsky.social said, always better to not have to think about catalogs and have it 'just work'

5/ fwiw, the S3 API is a standard of sorts, esp given that Cloudflare's equivalent service, R2, supports it. like @conormccarter.bsky.social said, if R2 (and Azure Blog, and GCP storage) support a table bucket style, we're moving towards standard interface/primitive bsky.app/profile/cono...

Conor McCarter@conormccarter.bsky.social

This also feels like something Cloudflare should do on top of R2 only with an Iceberg REST catalog implementation. To me, it actually feels more like the type of product that Cloudflare has been shipping, and would be a nice compliment to their serverless D1 database (~SQLite for up to 10GB)

2/ lately, I've been stoked more on the Iceberg REST catalog than the table format itself bc it radically simplifies things both for A. end users: in terms of what they need to know B: data platforms: in terms of the number standalone integrations needed

3/ half-baked comparison: maybe kinda like manufacturer-agnostic electric vehicle charging stations? bc: A. e-car buyer would want to know how prevalent is the network of compatible charging stations? B: e-car manufacturers prefer vehicles to be maximally compatible with various charging stations

Anders reposted

anyone have a good term to collectively refer to the data "languages" like #SQL, #polars, #pandas, #dplyr, #malloy, #preql #numpy etc? "data transformation APIs" (DTAPIs) is the best I've got so far but I'm dreaming of a better word #databs

3. Disruptive or Sustaining? over the next six years, what impact will recent innovations have on practitioners lives and the vendor ecosystem? Going deep specifically on OSS projects like: #iceberg, #substrait and Single-node compute (e.g. #DuckDB, #Datafusion) #databs

4. Hype to Reality: how to navigate new innovations in the data innovation: when to adopt, when to wait, how to help even if you can’t use it yet at work. Using my experience with #dbt, #iceberg, and #substrait. #databs

2. The Dispatches from the Future: Now that Cross-platform Mesh and Cost Optimization has shipped (will have by April 😅), what’s the next frontier for advancing the #ADLC for practitioners? Showcasing some early prototypes for how #dbt when both #Iceberg and #Substrait are in the mix #databs