Web2.0 - Mashing The Enterprise Up

Mashing the Enterprise Up Requirements for Enterprise Mashups April 24th 2008 Justo Hidalgo VP Technology [email_address] Web2Open

Agenda
Background
Web mashups and Enterprise Data Mashups
Requirement areas
Further thoughts

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

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

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

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

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

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

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?

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

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
…

Q&A Justo Hidalgo VP Technology [email_address]

http://l-y-e.blogspot.com	36
http://www.loscuentosdelabuelo.com	13
http://l-y-e.blogspot.com.es	8
http://justohidalgo.blogspot.com	6
http://www.adynammic.com	4
http://www.slideshare.net	3
file://	1

Web2.0 - Mashing The Enterprise Up

by Justo Hidalgo on Apr 24, 2008

Accessibility

Categories

Tags

Upload Details

Usage Rights

7 Embeds 71

Statistics

Web2.0 - Mashing The Enterprise Up — Presentation Transcript