Crossing the Mashup Chasm. Enterprise Mashup Requirements

1,970 views
1,892 views

Published on

Discussion at the Mashup Camp VI on March 20th, 2008. What´s the present and future of data mashups in an enterprise environment?

Published in: Technology
2 Comments
1 Like
Statistics
Notes
  • Hi! So sorry I missed your question!!!! In a very basic way, ETL is more focused on batch-based processes, where the number of sources is typically low, and the amount of data to transfer is huge. Data Virtualization, on the other side, gets the most value when you need real-time data access and transformation, and/or the creation of a 'data access layer' which your business logic uses it to access data, therefore simplfying how corporate apps are done.
    You can find other presentations here or at denodo.com, and I am currently preparing a generic presentation called 'Why data virtualization' that I hope you find it interesting.

    And again, sorry for the delay!!!

    Justo
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • how's your platform different from ETL?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,970
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
0
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide

Crossing the Mashup Chasm. Enterprise Mashup Requirements

  1. 1. Crossing the Mashup Chasm Requirements for Enterprise Mashups March 20th 2008 Justo Hidalgo VP Technology [email_address] Juan Lozano Principal Software Engineer [email_address] ashupCamp.com
  2. 2. What am I looking for in this discussion?
  3. 3. Agenda <ul><li>Background </li></ul><ul><li>Web mashups and Enterprise Data Mashups </li></ul><ul><li>Requirement areas </li></ul><ul><li>Further thoughts </li></ul>
  4. 4. Background <ul><li>Justo N. Hidalgo </li></ul><ul><li>VP Technology Denodo Technologies, Palo Alto </li></ul><ul><li>Ph.D. Computer Science in Query Optimization in Mediators of Web Sources </li></ul><ul><li>Interest in how Enterprise Data Mashups evolve. </li></ul><ul><li>Juan Lozano </li></ul><ul><li>Principal Software Engineer Denodo Technologies, Palo Alto </li></ul><ul><li>Our “web wrapper” guru  </li></ul><ul><li>Product (Denodo Platform 4.1) </li></ul><ul><li>Enterprise Data Mashups & Web Automation </li></ul><ul><ul><li>Data Integration of Structured, Web and Unstructured Information </li></ul></ul><ul><li>Technology Focus: Data Integration, Web 2.0 & Mashup Enabler </li></ul><ul><li>Targeted Solutions: Intelligence, Single View, Web Automation </li></ul><ul><li>Tenths of projects in the last 12 months to learn from </li></ul>
  5. 5. Web Mashups vs. Data Mashups <ul><li>Web Mashups </li></ul><ul><li>Visual centric </li></ul><ul><li>Data relationships are simple </li></ul><ul><li>End-user driven enabled by APIs / tools </li></ul><ul><li>No QoS guarantees – as is </li></ul><ul><li>Simple Web security </li></ul><ul><li>Data Mashups </li></ul><ul><li>Data & Information centric </li></ul><ul><li>Deep transformations & semantic relationships </li></ul><ul><li>Interact with Enterprise ecosystem </li></ul><ul><li>Business analyst driven w/ user control options </li></ul><ul><li>Enterprise QoS- Query Optimization, Reliable, Failover, etc. </li></ul><ul><li>Policy-based security </li></ul>ENTERPRISE ECOSYSTEM Enterprise Infrastructure / Web Platform Enterprise & Web Applications RIA, Social Software, GUI, Portals
  6. 6. 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 ?
  7. 7. Customer Uses of Enterprise Data Mashups 1. Aggregate Data 3. Exchange Data Enterprise Suppliers Customers 2. Enrich Data Apps Data Services
  8. 8. Requirement Areas: Mashups for Business Users / For Power Users and IT <ul><li>User experience </li></ul><ul><li>Heterogeneous granularity for different levels </li></ul>
  9. 9. Requirement Areas: Enterprise-class features… <ul><li>Security </li></ul><ul><ul><li>LDAP access, user and role permission levels, </li></ul></ul><ul><ul><li>But also: Secure VPNs, secure communications, encryption </li></ul></ul><ul><ul><li>EXAMPLE: Financial Aggregation </li></ul></ul><ul><li>HA/Scalability </li></ul><ul><ul><li>Load balancing </li></ul></ul><ul><ul><li>Federated and distributed architectures </li></ul></ul><ul><ul><li>EXAMPLE: TELE-2/Vodafone Call Center </li></ul></ul><ul><li>Performance </li></ul><ul><ul><li>Asynchronous access </li></ul></ul><ul><ul><li>Parallelism </li></ul></ul><ul><ul><li>Execution Plan Optimization techniques </li></ul></ul>
  10. 10. Requirement Areas: …Enterprise-class features <ul><li>Data Transformations </li></ul><ul><ul><li>Biopharma example: contextual summaries, patterns and regular expressions </li></ul></ul><ul><ul><li>LinkedForce example: textual similarity </li></ul></ul><ul><li>Maintenance </li></ul><ul><ul><li>Sources change… specially Web Sites!!! </li></ul></ul><ul><li>Data Management… don´t get me started  </li></ul><ul><ul><li>What are the boundaries between mashups and MDM, Data Quality tools? </li></ul></ul>
  11. 11. Requirement Areas: Ecosystem SOURCES: WEB, PACKAGED APPS, MAINFRAME, … DATA QUALITY, METADATA, STANDARDS REST, SOAP, MQSERIES, ESB, JDBC, JSR-168
  12. 12. Further thoughts <ul><li>“ Semantic mashups”: </li></ul><ul><ul><li>Automatic schema matching </li></ul></ul><ul><ul><li>Automatic Browsing and Information Structuring </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><li>“ Real Time” mashups </li></ul><ul><ul><li>I mean… HARD REAL TIME. </li></ul></ul>
  13. 13. Thank You! Justo Hidalgo, VP Technology Email [email_address] Juan Lozano, Principal Software Engineer Email [email_address] http://www.denodo.com

×