Revision as of 21:43, 5 January 2008 edit WBardwin (talk \| contribs) Pending changes reviewers, Rollbackers 20,628 edits mNo edit summary ← Previous edit		Revision as of 17:50, 1 February 2008 edit undo DamsonDragon (talk \| contribs) 110 edits corrected some grammatical errors, also added reference to ESB article Next edit →
Line 6: * EAI ([[Enterprise Application Integration]]) implementations * SOA ([[Service-Oriented Architecture]]) implementations * ESB ([[Enterprise Service Bus]]) implementations Core data integrations are often designed ~~with~~ to be enterprise-wide integration solutions. They may be designed to provide a data abstraction layer, which in turn will be used by individual core data integration implementations, such as ETL servers or applications integrated through EAI. Because it is difficult to promptly roll out a centrally managed data integration solution that anticipates and meets all data integration requirements across an organization, IT engineers and even business users create edge data integrations, using technology that may be incompatible with that used at the core. In contrast to a core data integration, an [[edge data integration]] is not centrally planned and ~~which~~is ~~will probably be~~generally completed with a smaller budget and a tighter deadline.

Core data integration: Difference between revisions