03 — Visual Memory Map & Framework Atlas
Attempt each map from memory before checking the answer line.
Map 1 — DII Outcome Spine
Rebuild: Need → Analyze → Design → Build → Operate.
Answer check:
Need → requirements + discovery + lineage + profiling + rules → architecture + models + mapping + orchestration → services + flows + migration + publication + CEP → monitor + Metadata + governance
Meaning: DII manages meaning, timing, dependencies and service—not merely byte movement.
Map 2 — ETL vs ELT
ETL: Source → Extract → Transform → Load → Target
ELT: Source → Extract → Load raw → Transform in Target
Circle the position of Transform.
Map 3 — Latency Ladder
Higher latency: Batch/scheduled → Micro-batch → CDC / near-real-time / event-driven → Very low: streaming and, where required, synchronous
Add the trade-off: lower latency can increase cost, dependency and complexity.
Map 4 — Interaction Complexity
Point-to-point: direct pairwise links; proliferation as systems grow.
Hub-and-spoke: systems ↔ common hub/canonical format.
Publish-subscribe: producer → topic/service → multiple subscribers.
Map 5 — Coupling
Tight: waits → shared availability → blocking risk
Loose: message/queue → independent operation → retry/resilience
Map 6 — Architecture Family
- EAI: defined application interfaces/APIs.
- ESB: message-oriented intermediary.
- SOA: reusable independent services.
- CEP: event streams/patterns → meaning → triggered action.
Map 7 — Virtual Access
- Federation: combined access to disparate stores.
- Virtualization: heterogeneous stores presented as one logical DB/view.
- DaaS: governed data/services delivered on demand.
None automatically implies physical warehouse persistence.
Map 8 — Plan & Analyze
1 Requirements → 2 Discovery → 3 Lineage → 4 Profiling → 5 Business Rules
Interpretation: know the need, find the sources, trace movement, test actual data, define expected behavior.
Map 9 — Design
Architecture → Interaction/services → Model hubs/interfaces/messages → Mapping → Orchestration
- Architecture chooses patterns and operating constraints.
- Models define persistent/transient structures.
- Mapping defines source-target conversion.
- Orchestration defines order/dependencies/triggers/recovery.
Map 10 — Develop
Data Services | Data Flows | Migration | Publication | CEP
- Services expose reusable capabilities.
- Flows implement schedules/subscriptions/events.
- Migration performs controlled conversion.
- Publication intentionally makes new/changed data available.
- CEP recognizes event patterns and acts.
Map 11 — Governance Trust
Business Meaning + Evidence + Permission + Reliability + Control
- Meaning = rules/transformations.
- Evidence = Metadata + lineage.
- Permission = sharing agreement / MOU.
- Reliability = SLA + continuity/recovery expectations.
- Control = approvals, reviews, monitoring.
Map 12 — Metrics
Availability | Volume & Speed | Cost & Complexity
Ask:
- Is requested data usable when needed?
- How much moves, how fast and with what latency?
- How many interfaces/technologies/support paths exist, and are shared services reused?
Final visual test
Rebuild Maps 3, 4, 6, 8, 9, 11 and 12 without looking. For each, change one fact and explain why the correct classification/design changes.