7. Customer 360 tradeoffs

Balance normalized operational data against analytics-ready access patterns for a customer 360 model.

Constraints

Keep identity, contactability, account history, and event context coherent without creating a monolithic customer table

Brainstorming scratchpad

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

AI review panel

Validate the ERD objects to inspect keys, names, and cardinality coverage.