| 1 |
Integration |
Interoperability |
movement/consolidation vs ability of systems to communicate |
| 2 |
ETL |
ELT |
Transform before Load vs Load raw then Transform in target |
| 3 |
Snapshot |
Delta |
point-in-time set vs changes since prior transfer |
| 4 |
Batch |
Micro-batch |
scheduled larger groups vs same pattern at higher frequency |
| 5 |
CDC |
Replication |
detect/pass deltas vs maintain synchronized copies |
| 6 |
Data-based CDC |
Log-based CDC |
data/application indicators vs DBMS activity logs |
| 7 |
Asynchronous |
Synchronous |
sender continues vs current process waits |
| 8 |
Near-real-time |
Real-time synchronous |
small delay allowed vs no acceptable delay/current process blocks |
| 9 |
Streaming |
Batch |
continuous events vs periodic sets/files |
| 10 |
Replication |
Semantic integration |
copy same data vs reconcile meaning/structure |
| 11 |
Point-to-point |
Hub-and-spoke |
direct pair links vs common hub/control point |
| 12 |
Hub-and-spoke |
Publish-subscribe |
common exchange hub vs publish once/multiple subscribers |
| 13 |
Canonical model |
Source-specific message |
shared enterprise format vs one-off pair-specific format |
| 14 |
Tight coupling |
Loose coupling |
shared availability/dependency vs independent operation |
| 15 |
Mapping |
Orchestration |
field/rule conversion vs process order/dependencies |
| 16 |
Orchestration |
Process controls |
flow execution pattern vs logs/alerts/exceptions/dependency evidence |
| 17 |
EAI |
ESB |
API-mediated application interaction vs message intermediary |
| 18 |
ESB |
SOA |
bus implementation vs architecture of reusable independent services |
| 19 |
SOA |
API |
service architecture vs interface mechanism often used to expose service |
| 20 |
ESB |
CEP |
move/route messages vs interpret event patterns and trigger response |
| 21 |
Federation |
Virtualization |
combined access across stores vs present heterogeneous stores as one logical DB |
| 22 |
Virtualization |
Physical consolidation |
no required persistence vs data stored in common physical structure |
| 23 |
DaaS |
Database-as-a-Service |
data delivered as service vs database infrastructure delivered as service |
| 24 |
Cloud integration/iPaaS |
On-prem ESB |
cloud-delivered integration vs internally deployed middleware |
| 25 |
Discovery |
Profiling |
find/identify candidate sources vs analyze actual content/fitness |
| 26 |
Profiling |
Data Quality program |
integration-focused inspection vs broader ongoing quality management |
| 27 |
Lineage |
Mapping |
origin/movement/change history vs source-target transformation specification |
| 28 |
Business rule |
Mapping rule |
business constraint/derivation vs how a source value becomes a target value |
| 29 |
Requirements |
Architecture |
what/why constraints vs how solution patterns/components meet the need |
| 30 |
Data service |
Data flow |
reusable access/update capability vs execution path of integration steps |
| 31 |
Migration |
Publication |
controlled move for application change vs producer makes new/changed data available |
| 32 |
Migration |
Operational integration |
repeated trial/final conversion vs ongoing exchange |
| 33 |
Metadata repository |
ETL tool |
stores meaning/rules/lineage/process Metadata vs executes movement/transformation |
| 34 |
Data Sharing Agreement |
Technical interface spec |
use/responsibility/service obligations vs technical exchange definition |
| 35 |
SLA |
Sharing Agreement |
performance/service commitment vs broader acceptable-use/responsibility/restrictions |
| 36 |
Forward lineage |
Backward lineage |
where data is used/goes vs where it came from |
| 37 |
Enterprise reuse |
Local one-off |
fewer reusable standard components vs local speed with proliferation/support risk |
| 38 |
Business accountability |
Technical implementation |
approves meaning/transformation rules vs implements governed rules |