Rapid Recall Key — 27–51

1. ESB: message-oriented intermediary routing/mediating/transformation among heterogeneous systems, often async/near-real-time.
2. SOA: architecture of independent reusable services with well-defined contracts/interfaces and hidden implementation.
3. CEP: combine/interpret multiple events or streams to identify meaningful condition and automatically trigger action.
4. Federation = combined access across disparate stores; Virtualization = present heterogeneous distributed sources as one logical DB/view without necessary physical consolidation.
5. DaaS: governed data made available on demand as a service internally or externally.
6. iPaaS/cloud integration: cloud-delivered integration spanning SaaS, cloud, on-prem and/or B2B contexts.
7. Data exchange standard = formal/shared structure and meaning for exchange to which participants map.
8. Plan & Analyze: requirements; discovery; lineage; profiling; business rules.
9. Discovery finds candidate sources/what exists; Profiling inspects actual content/structure/nulls/ranges/patterns/fitness.
10. Lineage records origin, movement, transformation, destination/use/frequency and supports troubleshooting/impact analysis/duplication detection.
11. Business-rule categories: definitions, facts, constraints/action assertions, derivations.
12. Design: integration architecture/interaction model; services/exchange patterns; model hubs/interfaces/messages/services; source-target mapping; orchestration.
13. Mapping = what source becomes what target; Orchestration = when/in what order/dependency/trigger processes execute.
14. Develop: data services; data flows; migration approach; publication approach; CEP flows.
15. Migration may be one-time in business intent but requires repeated analysis, trial conversions, reconciliation/testing and cutover preparation.
16. Publication defines how producers intentionally make new/changed data available to hubs/buses/consumers on schedules/events, preferably using common messages/services.
17. CEP prepares context/history as needed; processes real-time events; detects meaningful conditions with rules/thresholds; triggers actions.
18. DII Metadata: structures/semantics, mappings, business/transformation rules, schedules/frequency, dependencies/triggers, processing history, service definitions/registry, lineage.
19. Seven tools: ETL/transformation engine; virtualization server; ESB; business-rules engine; data/process modeling; profiling; Metadata repository.
20. Loose coupling improves independent availability/resilience because one system need not automatically stop when another is unavailable.
21. DII CoE centralizes/reuses integration expertise, standards, patterns and support knowledge while local teams may retain operations.
22. Business stakeholders/Data Stewards own transformation meaning; technical teams implement approved rules.
23. Data Sharing Agreement/MOU: responsibilities, acceptable use, restrictions, expected service/availability/response and other conditions of exchange.
24. Backward lineage asks where target came from/how transformed; forward lineage asks where source/rules are used downstream and what a change affects.
25. Metrics: Data Availability; Data Volumes & Speed/Latency; Solution Costs & Complexity/Usage.

← Key 01–26 · Blank-Page Reconstructions →