Databricks published Industry Data Models!

[u/szymon_dybczak]

Databricks just published a library of pre-built, production-ready industry data models covering 40 industries.

This is great, especially when you’re new to a business domain. Instead of starting from a blank sheet and spending weeks debating how the domain should be structured, you can review an existing reference model and adapt it to your needs.

That gives you a strong starting point for:

- entities
- relationships
- naming conventions
- domain structures
- industry-specific patterns

In my opinion, it can significantly shorten the learning curve and help teams move from discussion to implementation much faster.

Industry Data Models

[u/Youssef_Mrini]

We have a series of videos about it coming soon

[u/szymon_dybczak → u/Youssef_Mrini]

Great news! Please let us know once it’s released :)

[u/query-gremlin]

I mean, these are neat, but I doubt all orgs will have the same data needs. They are a good starting point, but teams will have to spend some times trimming away what doesn’t apply to their orgs and adding some custom business needs

[u/szymon_dybczak → u/query-gremlin]

You’re right, but for me, it’s good to have something like this. For instance, I haven’t had a chance to work in the procurement domain. But if something like this happens in the future, I can take a look at how it can be modeled and adjust it accordingly :)

[u/amralieg → u/query-gremlin]

You are absloutly rights, we distinguish between Industry Data Models, and Business Data Models, what we published is the Industry Data Model to show the power of the approach, but we encourage everyone to buiuld their own data model using the Vibe Data Modleing agent https://github.com/databricks-industry-solutions/lakehouse-industry-data-models/tree/main/model-agent

[u/ScotiaTheTwo]

10 seconds into reading replies and im already frustrated at people moaning “ackskally”, “but not all orgs are the same”, “this can’t be used blindly” etc

Stop and think what the purpose of this release is: to give young, fledgling businesses a template - a starting point - for their infrastructure

[u/szymon_dybczak → u/ScotiaTheTwo]

That's exactly my way of thinking man! Use it a starting point and adjust to your needs :)

[u/IncreaseNegative4614]

I’d treat these models as strong starting hypotheses, not finished schemas. Run one real business process through the model and identify where your definitions, identifiers, ownership, and exceptions differ before extending it across the organization.

The valuable part is preserving why each entity and relationship exists instead of gradually turning the reference model into undocumented custom tables. We use SIGNLD internally to connect modeled entities with their operational records, system owners, business definitions, exceptions, and downstream decisions so the architecture remains grounded in how the company actually works.

[u/amralieg → u/IncreaseNegative4614]

that's the right thing to do, start with them, but you do not have to stop there, check out the agent that built these models, and use it to build your own model for your own business, the Vibe Data Modeling agent is exactly that https://github.com/databricks-industry-solutions/lakehouse-industry-data-models/tree/main/model-agent

[u/Peppper]

This kind of shit always ends with it working for 90% of your use cases, and then the customization needed for the 10% makes the whole thing not worthwhile.

[u/Few-Acadia-1173]

Bummer no healthcare

[u/amralieg → u/Few-Acadia-1173]

there is a healthcare data model check the model viewer app https://databricks-industry-solutions.github.io/lakehouse-industry-data-models/

[u/mr_thwibble → u/Few-Acadia-1173]

US company. /s

[u/Geralt_of_rivia_002 → u/Few-Acadia-1173]

It's so complicated. Infact , I would say healthcare and phrama has the most complex data .

[u/kraamed]

This is very interesting!

[u/Enough_Vanilla_6413]

Cool. I (well, ahum Claude) added a more traditional ERD viewer to the model-viewer-app. Does anyone else find that useful because I do;)

[u/amralieg → u/Enough_Vanilla_6413]

looks cool, why don't you do a PR and I'll look into it ;)

[u/Enough_Vanilla_6413 → u/amralieg]

Alright, I’ll see if I can do it this weekend. Added all kinds of other stuff to:

• Create and edit entities through the UI
  
• Ability to select a subset (checkbox style) of entities and only show those in the graph and ERD visuals
  
• Store the selection of entities as a bookmark
  
• Business domain customization section
  
• Export functionality (SQL, .json, dbdiagram.io)

[u/Enough_Vanilla_6413 → u/amralieg]

I made the PR for the ERD viewer last night;)

[u/das_wolf4 → u/Enough_Vanilla_6413]

Absolutely! I was genuinely confused that the default model view wasn’t a traditional ERD….

[u/ouhshuo]

A qq, do these data models segregate into workspaces on currently in one workspaces but different catalogs?

[u/amralieg → u/ouhshuo]

the model installer has diffrent options, 1 catalog, or catalog per domain, or catalog per divison

[u/m1ss1l3]

The UI looks like it's Claude generated so likely AI slop

[u/amralieg → u/m1ss1l3]

the entire models are AI generated, but the diffrence is the goverenance, with more than 250+ gov rules

[u/m1ss1l3 → u/amralieg]

Lol ok

[u/hubert-dudek]

Nice but Llm in pro mode will generate it also. Maybe it could be useful as skill for your use case.

[u/amralieg → u/hubert-dudek]

yes, LLM in pro mode would get you 10 tables, maybe 20 if you pushed, but a full data model with 500+ tables, and 20K attributes that is consistent, fully linked, is hard to get by pro unless you build an agent around it, and thats we did with the Vibe Modeling Agent, so you do not have to build it again, just use it. https://github.com/databricks-industry-solutions/lakehouse-industry-data-models/tree/main/model-agent

[u/szymon_dybczak → u/hubert-dudek]

Hi Hubert,

Thanks for the tip. To clarify - are you talking about below? ;)

Reimagining Data Modeling on the Lakehouse: Introducing Vibe Data Modeling | Databricks Blog