LinkedIn profile ↗
Why does this site exist?
Databricks renames its products often. The old names stay in blogs, courses, and people's heads. You search for one and get lost. REbricked tells you what it is called now.
Why does a name matter?
A wrong name costs more than time. You may build on something that is already deprecated. You may miss the feature that replaced it.
What can I find here?
Renames, deprecations, and new features. The name says it: renamed or deprecated.
Search an old name. You get the new name, the date, and the proof. Every name a product ever had gets its own card.
Why can I trust it?
Every entry links to an official Databricks or Microsoft Learn page. Each one shows the date we last checked it. No source, no entry.
Is anything made up?
The fun facts are true, and each has a source. Only the predicted next names are made up. They are always labelled.
What else is here?
The guides explain what to do about a change. The quiz tests how many new names you know. The RSS feed sends you each new change. There is a Snowflake edition too.
Is this an official Databricks site?
No. REbricked is an independent, educational project. It is not affiliated with Databricks. The console look is an homage. Read the full disclaimer.
How do I fix a mistake?
Found an old name, a missing rename, or a dead link? Open an issue or a pull request on GitHub ↗. Each entry is one small file, so fixes are easy.
Who makes it?
Databricks community experts build REbricked. See the full list of contributors on GitHub ↗.

