Web2.0 - Mashing The Enterprise Up

Slide 1: Web2Open Mashing the Enterprise Up Requirements for Enterprise Mashups April 24th 2008 Justo Hidalgo VP Technology jhidalgo@denodo.com www.denodo.com

Slide 2: Agenda s Background s Web mashups and Enterprise Data Mashups s Requirement areas s Further thoughts

Slide 3: Background Justo N. Hidalgo VP Technology Denodo Technologies, Palo Alto Ph.D. Computer Science in Query Optimization in Mediators of Web Sources Product (Denodo Platform 4.1) Enterprise Data Mashups & Web Automation Data Integration of Structured, Web and Unstructured Information Technology Focus: Data Integration, Web 2.0 & Mashup Enabler Targeted Solutions: Intelligence, Single View, Web Automation Tenths of projects in the last 12 months to learn from

Slide 4: Web Mashups vs. Data Mashups Web Mashups Data Mashups Visual centric Data & Information centric Data relationships are simple Deep transformations & semantic End-user driven enabled by APIs / relationships tools Interact with Enterprise ecosystem No QoS guarantees – as is Business analyst driven w/ user Simple Web security control options Enterprise QoS- Query Optimization, Reliable, Failover, etc. Policy-based security ENTERPRISE ECOSYSTEM RIA, Social Software, GUI, Portals Enterprise & Web Applications Enterprise Infrastructure / Web Platform

Slide 5: Mutual Benefits ENTERPRISE ECOSYSTEM RIA, Social Software, GUI, Portals BPM ESB EAI Enterprise & Web Applications Enterprise Infrastructure / Web Platform Web Mashups User experience / global access Data Mashups Enterprise Data Integration WEB DATA MASHUPS MASHUPS ETL Data Warehouses ? Enterprise-class features

Slide 6: Customer Uses of Enterprise Data Mashups 1. Aggregate Data 2. Enrich Data Apps Data Services 3. Exchange Data Suppliers Enterprise Customers

Slide 7: Requirement Areas: Mashups for Business Users / For Power Users and IT User experience Heterogeneous granularity for different levels

Slide 8: Requirement Areas: Enterprise-class features… Security LDAP access, user and role permission levels, But also: Secure VPNs, secure communications, encryption EXAMPLE: Financial Aggregation HA/Scalability Load balancing Federated and distributed architectures EXAMPLE: TELE-2/Vodafone Call Center Performance Asynchronous access Parallelism Execution Plan Optimization techniques

Slide 9: Requirement Areas: …Enterprise-class features Data Transformations Biopharma example: contextual summaries, patterns and regular expressions LinkedForce example: textual similarity Maintenance Sources change… specially Web Sites!!! Data Management… don´t get me started  What are the boundaries between mashups and MDM, Data Quality tools?

Slide 10: Requirement Areas: Ecosystem REST, SOAP, MQSERIES, ESB, JDBC, JSR-168 DATA QUALITY, METADATA, STANDARDS SOURCES: WEB, PACKAGED APPS, MAINFRAME, …

Slide 11: Further thoughts Need for a real enterprise mashup architecture Where IT and business are actually involved “Semantic mashups”: Automatic schema matching Automatic Browsing and Information Structuring …

Slide 12: Q&A Justo Hidalgo VP Technology jhidalgo@denodo.com