Home › Key concepts › Data map and owners
Key concept · Crawl (beginner) · the same on every platform
Data map and owners
Where the customer's data lives, what shape it is in, and who can say yes.
What it is
List each system the use case needs, what data it holds, how you get it (API, export, database), how good it is, and who owns access. Most delays in customer projects are access, not code.
Why it matters
It shows the real risks and timeline early.
An example
Claims in a policy system (API, good), emails in a shared mailbox (export, messy), photos in a file share (no owner yet).
The common mistake
Assuming you'll 'get the data' in week one.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Catalog and accesswho owns which table, who may read it, where it came from | Glue Data Catalog + Lake Formation | Microsoft Purview | Dataplex | Unity Catalog | OpenMetadata |
Related ideas
Where it shows up
Part of the Crawl level on these paths: Forward Deployed Engineering (understand).