There's no single official Databricks newsletter. Here's the full landscape, honestly compared, with a suggested setup at the end.
The minimum-viable setup for staying current on Databricks:
Everything below explains why those four. Skip ahead if you want the full landscape with comparisons.
Most enterprise platforms ship a single official weekly email, sometimes two. Databricks doesn't. The closest thing is the Databricks blog, which publishes daily-ish, but it has no cadence guarantee and no opinionated curation.
The result: anyone trying to stay current on Databricks ends up monitoring 5-10 surfaces themselves. The official blog. The official YouTube channel. The Community forum. The DAIS YouTube playlists. The GitHub releases for the SDKs, the Terraform provider, the dbt adapter, MLflow, Delta Lake, Unity Catalog OSS, and a handful of others. Reddit. Stack Overflow for production troubleshooting. The dbt Labs blog if you do transformations there. The MLflow blog if you ship ML.
The good news: most of these surfaces are public and well-maintained. The bad news: keeping up manually is a part-time job nobody pays for. Hence the rest of this guide, and the existence of brickster.ai itself.
Grouped by category. Each entry is a real public source with the cadence and format honestly characterised.
The official Databricks publication. Product announcements, customer stories, engineering deep-dives. Usually 1-5 posts per day during keynote weeks, 1-2 per week otherwise. The primary source most ecosystem coverage cites back to.
Tutorials, customer stories, and replays from Databricks-hosted events. Heavier on the how-to side than the news side. Best for going deep on a feature once you know it exists.
The annual conference. Over 1,200 talks across the 2020-2025 archive cover everything from platform fundamentals to customer architectures. The keynotes set the strategic direction for the next 12 months of Databricks releases.
Official forum (Khoros-powered). High signal for production-realistic questions, especially about edge cases that don't make it into docs. Databricks employees answer some questions directly.
What you're reading now. Independent community project that aggregates 40+ public sources (official blog, ecosystem GitHub repos, YouTube creators, DAIS, community forums) into a single searchable archive. Adds a public Databricks roadmap, an AI assistant grounded in the archive, and an MCP server for Claude Desktop / Cursor / Codex. Tuesday-morning weekly digest.
The MLflow project blog. Cross-cuts with Databricks for anyone doing ML on the platform, but maintains independent voice since MLflow is open-source and used outside Databricks too.
Delta Lake's project blog. Technical posts on the storage layer underneath the Databricks lakehouse. Increasingly relevant after the Tabular acquisition reshaped the table-format landscape.
dbt's blog. Increasing Databricks-specific content since the dbt-databricks adapter became the recommended workflow. Read alongside the Databricks blog when transformation patterns matter.
Independent subreddit. Mix of beginner questions, war stories, hiring posts, and the occasional product critique. Not as moderated as the official forum, which can be a feature or a bug depending on what you're after.
Production troubleshooting central. Most useful for narrowly-scoped technical questions where someone has already hit your exact error. Less useful for strategy / architecture questions.
Filtered view of Databricks-blog posts that hit HN. Comments often surface contrarian takes you won't find in the official narrative — worth checking after a major launch.
You don't need to follow everything. Pick a setup that matches what you actually do day-to-day.
We're biased, obviously. Here's the honest case for why brickster.ai exists alongside the official sources rather than replacing them.
All of it free, no signup, independent community project. Not affiliated with Databricks, Inc.
If you only have time for one thing: the Databricks blog is the irreplaceable primary source. Everything else is downstream synthesis of what they publish there.
If you have time for two things, add an aggregator on top so you're not also reading dbt's blog, MLflow's blog, Delta Lake's blog, three YouTube channels, the GitHub releases pages, and r/databricks separately. That's the gap brickster.ai exists to fill — most weeks, the digest catches things the official blog didn't cover (ecosystem GitHub releases, DAIS talk drops, community-thread patterns).
If you have time for three, add r/databricks. Production-reality voices that aren't paid by Databricks to be positive about the product. Counter-balance.
That's it. Skip the rest until you have a specific need (MLflow blog for ML deep-dives, DAIS playlists for keynote replays, Stack Overflow when you hit a specific error).
One curated Tuesday email covering the full week, free, no signup beyond your email address. Unsubscribe in one click.
