Published on March 22, 2009
How to Use the Right Tools for Operational Data Integration Mark R. Madsen – March, 2009 http://ThirdNature.net Attribution-NonCommercial-No Derivative http://creativecommons.org/licenses/by-nc-nd/3.0/us/
What We’re Asked For (simulation) Slide 2 March 2009 Mark R. Madsen
How It Makes Us Feel Slide 3 March 2009 Mark R. Madsen
How We Want to Feel Slide 4 March 2009 Mark R. Madsen
Spending Priorities in IT In 2007 and 2008 this is where the money went… but you can’t do most of these without data integration. Sources: CIO Insight Slide 5 March 2009 Mark R. Madsen
Technology Priorities in IT Data integration moved up to #3 spot for CIOs in 2008 Sources: CIO Insight Slide 6 March 2009 Mark R. Madsen
The Cost Problem Management Reacts To Source: IDC Slide 7 March 2009 Mark R. Madsen
Where We Often Are Today: Point to Point Typical scenario: • Disparate data • Heterogeneous sources • Point integration • Minimal reuse • No tools Databases Documents Flat Files XML Services ERP Applications Source Environments Slide 8 March 2009 Mark R. Madsen
The Desired Future State “Data as a platform” provides: • Standards-based interfaces • Single views of disparate source data • Single point of access / integration • Reuse of data …but you can’t achieve this by Data Platform writing more application code Databases Documents Flat Files XML Services ERP Applications Source Environments Slide 9 March 2009 Mark R. Madsen
Application versus Data Integration Application Data Integration Integration Managing the flow of Managing the flow of events data and access Standardizes the Standardizes the data transaction or service Tools abstract the Tools abstract the transport and system transport, system, endpoints representation and manipulation Must write code at Data structure, format endpoints to manipulate and manipulation is data abstracted Focus on code - data as Focus on data - data as a byproduct the product Reusable functions, not Reusable data, not data functions Slide 10 March 2009 Mark R. Madsen
Analytic versus Operation Data Integration Analytic Operational Most of a BI project’s effort is Most of an application project spent on data integration is focused on features, not DI Many disparate sources One or a few sources Generally unidirectional One-way or bidirectional Large data volumes Large data volume for some, small volume for others Usually loaded daily Often loaded more often, varies based on project type Low concurrency Low to high concurrency High latency Low to high latency Slide 11 March 2009 Mark R. Madsen
Architectural Models for Data Integration Physical Data Access Model Virtual Distributed Centralized Control Slide 12 March 2009 Mark R. Madsen
Consolidation Common operational DI scenarios where this model is appropriate: • Migrations • Upgrades • Consolidations • Managing master / reference data Characteristics: • Large data volumes to move or access • One time data movement • Usually unidirectional • Transformation or cleansing required Slide 13 March 2009 Mark R. Madsen
Propagation Common scenarios: • Copying data that can’t be accessed directly / remotely • Synchronizing data • Data cross-referencing • Infrequent / one-time extracts Characteristics: • Can be one-way or bi-directional • Often repetitive data movement • Medium to large data volume (but not always) Slide 14 March 2009 Mark R. Madsen
Federation Common scenarios: • Real-time / low latency data access • Security / regulatory requirements that prevent copying data • Impractical to create a central database (e.g. # sources, latency) • Centralized data services Characteristics: • One-way • Lower data volumes • Higher concurrency Slide 15 March 2009 Mark R. Madsen
Choosing Models There are some basic criteria and tradeoffs to consider: • Data currency vs. latency • Diversity of data sources • Data cleansing & transformation • Predictability of performance • Access to the same data is needed via different interfaces • Non-relational sources • Frequency of access • Data volumes • And more… Slide 16 March 2009 Mark R. Madsen
A Handy Comparison Chart Consolidation Model Criteria Physical Virtual Data currency Query performance / latency Frequency of access Diversity of data sources Diversity of data types Non-relational data sources Transformation and cleansing Predictability of performance Multiple interfaces to same data Large query / data volume Need for history / aggregation Slide 17 March 2009 Mark R. Madsen
Three Implementation Choices • Write code! It’s fun! It’s easy! At first. • Buy proprietary data integration tools • Use available open source tools Slide 18 March 2009 Mark R. Madsen
Hand-coded Integration Why is this so common? • DI is an afterthought on application projects • It’s just data • It’s hard to justify expensive tools for ODI • Developers and DBAs don’t talk The market is changing: • Lower tolerance for the high cost of custom DI development and maintenance • External data challenges • Bad fit for consolidation projects Products get better over time. Hand-written code gets worse. Slide 19 March 2009 Mark R. Madsen
Buying Data Integration Tools Buying is the usual alternative, mostly ETL tools. • ETL vendors are branching out • Many companies have ETL for BI But… • Poor fit for propagation and synchronization tasks • Centralized servers • Licensing costs / problems for consolidation tasks or broad use Integration code is single-purpose, tools are multi-purpose. You should always go with tools – when you can afford them. Slide 20 March 2009 Mark R. Madsen
Use of Tools vs. Hand Coding High Use Medium Use Low Use None 60% 50% 40% 30% 20% 10% 0% ETL EDR EII EAI ETL EDR EII EAI ETL EDR EII EAI ETL EDR EII EAI Source: TDWI, 2006 Slide 21 March 2009 Mark R. Madsen
Open Source: End of Buy vs. Build Open source avoids the pitfalls of coding and gains the advantages of using tools. • Tools can be distributed with little to no license restrictions • Application projects budget for features, not glue • Even basic tools have obvious operational advantages over hand-coding Why build custom code when there are comparable tools available? Slide 22 March 2009 Mark R. Madsen
Benefits Reported After your organization adopted open source software, what was the primary benefit of its use? Flexibility 31% Lower cost 31% Reduced dependence on vendors 15% Performance 10% Reliability 7% Security 4% Other 3% Source: The 451 Group Slide 23 March 2009 Mark R. Madsen
A Side Benefit of Flexibility Comparison of time taken to evaluate tools Source: Yankee Group Slide 24 March 2009 Mark R. Madsen
Recommendations 1. Differentiate between analytic data integration and operational data integration 2. Stop hand-coding unless the problem really is trivial, and this includes table replication and DBA SQL scripts 3. Use the right data integration model for the problem 4. Augment existing data integration infrastructure with open source 5. Make open source the default option for data integration tools Slide 25 March 2009 Mark R. Madsen
Creative Commons Thanks to the people who made their images available via creative commons: red pill blue pill - http://www.flickr.com/photos/rcrowley/2540057217/ red pill blue pill2 - http://www.flickr.com/photos/thomasthomas/258931782/ happy dog jumping in meadow - http://flickr.com/photos/cenz/16128560/ Writing code – http://flickr.com/photos/cdm/72250667/ Woodworking – http://flickr.com/photos/rigoletto/126367565/ Febo – http://flickr.com/photos/jshyun/1573065713/ open_air_market_bologn - http://flickr.com/photos/pattchi/181259150/ Slide 26 March 2009 Mark R. Madsen
Thanks Slide 27 March 2009 Mark R. Madsen
Creative Commons This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/us/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. Slide 28 March 2009 Mark R. Madsen
Presentación que realice en el Evento Nacional de Gobierno Abierto, realizado los ...
In this presentation we will describe our experience developing with a highly dyna...
Presentation to the LITA Forum 7th November 2014 Albuquerque, NM
Un recorrido por los cambios que nos generará el wearabletech en el futuro
Um paralelo entre as novidades & mercado em Wearable Computing e Tecnologias Assis...
Get a definition of operational data integration, ... How do operational data integration and analytical ... back use of data integration tools;
Webcast on data integration outside the data warehouse in operational contexts and how open source fits in this area. If you want to download the slides or ...
Talend's data integration tools feature over ... the use of data and ... or batch to meet both operational and analytical data integration ...
Laura Madsen; Mark Madsen; Susan ... under "How to Use the Right Tools for Operational Data Integration" on ... that favor use of tools for operational ...
... data integration tools help ... competitive and operational aspects of the enterprise. Data volumes ... of use, and integration with Oracle Master Data ...
It might be time to reassess that strategy and look at data integration tools, ... data integration tools have specialized use ... tools, is the right ...
Big Data Tools for Developers. ... Getting the Right Tools for Data Integration. ... for operational integration while at the same time helping them to ...
Data integration tools address a wide range of use cases that rely on key data delivery ... these capabilities and pick the right tools for ...
I uploaded the slides from last's week's webcast on operational data integration and open source. They're embedded below for online viewing. This is an ...