August 17, 2006. Call in at 12:55 p.m. Eastern Time
Upcoming SlideShare
Loading in...5
×
 

August 17, 2006. Call in at 12:55 p.m. Eastern Time

on

  • 265 views

 

Statistics

Views

Total Views
265
Views on SlideShare
265
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

August 17, 2006. Call in at 12:55 p.m. Eastern Time August 17, 2006. Call in at 12:55 p.m. Eastern Time Presentation Transcript

  • August 17, 2006. Call in at 12:55 p.m. Eastern Time Mike Gilpin Noel Yuhanna Vice President Senior Analyst Forrester Research Teleconference Information Fabric: Enterprise Data Virtualization
  • Theme Data architecture and its management are evolving toward an information fabric that delivers information as a service.
  • Agenda
    • Data management and integration challenges
    • SOA has arrived, bringing information as a service
    • Defining “information fabric”
    • Information fabric architecture
    • Vendor landscape
    • Case studies
    • Recommendations
  • Data challenges continue to grow
    • Data management challenges:
      • Growing data volume
      • Need for real-time information
      • Data security concerns
      • Growing complexity of systems
      • Increased HA requirement
      • Underutilized servers and storage
      • Drive toward enhanced SLAs
    • Distributed data challenges:
      • Integration issues
      • Manageability
      • Data duplication
      • Security concerns
      • Performance and scalability
      • Synchronizing repositories
      • Content, unstructured data
  • What do enterprises want?
    • Lower cost: Proliferating redundant data
    • Real-time information: Sharing for emerging apps
    • Quality: Consistent information, single truth of data
    • Agility: Quickly respond to new needs for information
    • Automation: Reduce ongoing development efforts
    • Availability: Support 24x7 requirements
    • Virtualization: Hide complexity of real data sources
  • SOA enables information as a service
    • Earlier generations of data integration still led to silos
    • Information as a service gives broader access to more information sources
    • SOA plus middleware enables this
    Source: Forrester Research ETL EII EAI Repli- cation Integration depth (but in silos) Integration breadth (across silos) Home- grown
  • But SOA is critically dependent on metadata Service life-cycle environment Core application platforms … Enterprise service bus Service command platform Service clients Service interfaces Control Change Connection Core services Service metadata
  • Warning: service-oriented chaos wreaks havoc on SOA payback
    • You can’t reuse what you can’t find — bringing needless duplication.
    • Chaotic service metadata becomes a huge problem.
    • A chaotic information model reduces value of information provided through the SOA infrastructure (e.g., ESB).
    • Organizations often lack the processes and technology to avoid
    • service and information chaos.
  • What is information fabric?
    • An information fabric presents a business-friendly virtual view of diverse information. Information is provided in the form that applications and users need, hiding the complexity of the underlying sources. Information is accessed through the fabric, enabled by distributed middleware.
  • Information fabric: conceptual view Users & apps Info fabric Info sources Computers Databases Integration Catalog Security Applications Portals Other fabrics Discovery Files Backups End users Events Management Storage Network Virtual view of enterprise information
  • Information fabric: physical view
        • Distributed information access
    Policies Distributed, federated metadata repositories Business rules Database Files
        • Distributed cache
    Applications XML/SOAP Devices SQL/ODBC-JDBC Database Files Devices Integrated data management Transactional apps Decision support apps B2B apps Web services Content mgmt apps RFID Unstructured content Structured data Semistructured data
  • Where do I get one?
    • Nobody has the whole thing — yet.
    • Some large enterprises are building their own fabric.
    • Each player brings a different subset of strengths.
    • Leaders in data middleware, caching, DBMS, SOA, and ESBs, plus some emerging specialists, have the inside track.
    • The pieces are coming together through acquisitions or engineering development, by late 2007 . . .
    • . . . but you can do much of this today.
  • Some of the vendors in the game Partial Yes Yes No MetaMatrix No Partial No Yes DataSynapse No Partial No Partial Kx Systems Partial Partial Partial Yes GemStone Systems Partial Partial Partial Yes GigaSpaces No Partial No Yes Terracotta Partial Partial Partial Yes Tangosol Partial Yes Partial Yes Sybase Partial Partial No No Microsoft Partial Yes Partial Partial IBM Partial Partial No No Oracle Partial Yes Yes Yes BEA Systems Integrated data management Distributed information access Distributed metadata repository Distributed cache
  • Case study: telco
    • Background:
      • Manageability and integration issues
      • Legacy and distributed applications
      • Wanted to simplify IT architecture and lower cost
    • Solution:
      • BEA and other homegrown solutions
      • Currently working to put together the solution
      • Enabled it to accelerate time-to-market by moving to component-based development for new applications
  • Case study: financial services
    • Background:
      • Replicated data between two data centers
      • Increased transactions and requirements
      • Supported load balancing, high availability, and integration issues
    • Solution:
      • Developed integration components internally
      • Used GemStone for distributed data cache
      • Lowered cost through better server utilization and improved availability and performance
  • Recommendations
    • Start small; incrementally grow toward information as a service.
    • Data security must be a top priority.
    • Ensure performance as you go.
    • Keep it in SOA context — information fabric is a means to an end, promoting information as a service.
    • But a full information fabric is a longer-term vision.
  • Thank you Mike Gilpin [email_address] www.forrester.com Noel Yuhanna [email_address]