Next Generation Internet Services
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Next Generation Internet Services

on

  • 467 views

 

Statistics

Views

Total Views
467
Views on SlideShare
466
Embed Views
1

Actions

Likes
0
Downloads
4
Comments
0

1 Embed 1

http://www.slideshare.net 1

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

Next Generation Internet Services Presentation Transcript

  • 1. Next Generation Internet Services Dean Jacobs Technische Universität München
  • 2. Talk Outline
    • Web 2.0 and Consumer Services
    • Enterprise Software as a Service
    • Case Study: salesforce.com
    • Database Virtualization
  • 3. What Is Web 2.0
    • The Web As Platform
    • Harnessing Collective Intelligence
    • Data is the Next Intel Inside
    • End of the Software Release Cycle
    • Lightweight Programming Models
    • Software Above the Level of a Single Device
    • Rich User Experience
    Tim O'Reilly 2005
  • 4. 1. The Web As Platform
    • Seamless cooperation (mashups) between services
      • Google maps + Craig’s List = housingmaps.com
      • An ecosystem of interdependent services
    • Reach the “long tail” of users
      • Exploit self-service and algorithmic data management
      • Google AdSense rather than DoubleClick ($3.1B)
    • Easy to experiment
      • Low cost for failure
      • Fostering a huge wave of innovation
  • 5. 2. Harnessing Collective Intelligence
    • People perform tasks for themselves, the community, or both (reputation building)
    • Computers amplify the data into significant value
    • Google Page rank
    • Ebay Supply chain
    • Wikipedia , MySpace, Flickr User-generated content
    • Flickr , del.icio.us Tagging for classification
    • ESP Game Two-person game that tags photos
    • Digg Vote to determine importance of news stories
    • Last.fm Song recommendations from listening patterns
    • HSX Hollywood predictive market
    • Amazon Customer ratings and reviews
    • Amazon Mechanical Turk Hire people for simple tasks
  • 6. 3. Data is the Next Intel Inside * Streaming Data: “The Live Web” Amazon ?? Market Basket* Flickr Photographer Photographs* Google ?? Browsing Activity* Amazon Amazon Product Reviews* Amazon ISBN Book Numbers* E*Trade Stock Markets Stock Valuations* Google Maps Digital Globe Satellite Images Zillow County Records Home Valuations* Google Maps NavTeq Maps Enhancement Ownership
  • 7. 4. End of the Software Release Cycle
    • Software is offered as a service not a product
    • Operations become a core competency
      • As important to Google as PageRank
    • Perpetual beta
      • Weekly or even daily updates
      • Real-time monitoring of user behavior
    • Dynamic scripting languages (Perl, Python, PHP, Ruby) are more nimble and therefore more suitable
  • 8. 5. Lightweight Programming Models
    • Started with HTTP/HTML and lead to Web Services
      • Also applies to the design of Web Services APIs
    • Loose coupling is essential
      • Make few assumptions about the other end
      • Be self-describing and resilient to changes
    • Simple, flexible protocols are better than complex, specialized protocols
      • Amazon reports 95% of their Web Services traffic uses REST (XML over HTTP) rather than SOAP
      • SOAP and WS-* are designed for Enterprise Application Integration
  • 9.
    • 6. Software Above the Level of a Single Device
      • Applications should span servers, desktops, laptops, cell phones, PDAs, and special devices
      • Example: iPod/iTunes reaches from the handheld device to a massive web back-end with the PC acting as a local cache and control station
    • 7. Rich User Experience
      • Rich Internet Applications started with browser Applets
      • Realized today as AJAX
    • “ AJAX isn't a technology. It's really several technologies, each flourishing
    • in its own right, coming together in powerful new ways. AJAX incorporates:
      • standards-based presentation using XHTML and CSS;
      • dynamic display and interaction using the Document Object Model;
      • data interchange and manipulation using XML and XSLT;
      • asynchronous data retrieval using XMLHttpRequest;
      • and JavaScript binding everything together.“
    • Jesse James Garrett - Adaptive Path
  • 10. Talk Outline
    • Web 2.0 and Consumer Services
    • Enterprise Software as a Service
    • Case Study: salesforce.com
    • Database Virtualization
  • 11. Enterprise Software Models Data Center Application Service Provider System Integrators Customers Open Source Platform Vendors System Integrators On-Premises Software Software as a Service Application Vendors Customer Data Center
  • 12. Web 2.0 Checklist Data Center Application Service Provider Customers
    • The Web As Platform
    • Harnessing Collective Intelligence
    • Data is the Next Intel Inside
    • End of the Software Release Cycle
    • Lightweight Programming Models
    • Software Above the Level of a Single Device
    • Rich User Experiences
    5 1 5 System Integrators 1 7 6 4 3 2 5 1 Hosted Services On-premises Applications
  • 13. Lower Total Cost of Ownership
    • Leverage economy of scale
      • Capital expenditures – hardware, software
      • Operational expenditures – bandwidth, personnel
    • Leverage open-source software
      • Natural fit for a service-oriented model
    • One version of the software
      • Runs on only one platform
      • Upgrade all users at the same time (rolling upgrade)
    • Tight coupling of operations and support
      • Resolve customer issues on the production system
      • Perform professional services on the production system
  • 14.
    • An application is more attractive to host if …
      • Leverages Internet connectivity
      • On-premises solutions expensive
      • Less data and simpler operations
      • Simpler configuration
      • Simpler backend integration
      • Weaker transactional requirements
      • Weaker security requirements
      • Less mission critical
    Hosting Sweet Spots Apply more to People Apps Sales, Marketing, HR, Help Desk, Portal than Process Apps Planning, Purchasing, Inventory, Financials, Manufacturing Apply more to small to mid-sized businesses Opening up new markets Limits on functionality
  • 15. Sacrificing Functionality Functionality Total Cost of Ownership Scalability Using on-premises software The sweet spot Not worth building Not possible to build
  • 16. Talk Outline
    • Web 2.0 and Consumer Services
    • Enterprise Software as a Service
    • Case Study: salesforce.com
    • Database Virtualization
  • 17. The Primary Application
    • Customer Relationship Management (CRM)
      • Marketing and Campaign Automation
      • Salesforce Automation
      • Customer Service and Support
      • Analytics and Reporting
    Hosted CRM Market Share - IDC Worldwide On-Demand CRM Vendor Analysis, 2005 50% 7% All others 14% 7% salesforce 18% 4% #2 #3 #4 #5
  • 18. The Web As Platform
    • Web Services API to access salesforce objects
      • End users: strongly-typed for organization data model
      • Developers: weakly-typed to span organization models
    • Simple and scalable
      • REST model to reduce server-side state
      • Bulk operations to reduce communication overhead
    • Used to integrate with
      • the ecosystem of partner services
      • on-premises applications in enterprise data centers
      • clients: browser (AJAX), off-line edition, mobile devices, spreadsheets, calendar
  • 19. Harnessing Collective Intelligence
    • A set of extensions can be packaged into an installable application by customers and SIs
    • Project management, expense tracking, budgeting, purchasing, HR, education, manufacturing, …
    • Targets the “long tail” of custom applications
  • 20. Service Growth 1999 2000 2001 2002 2003 2004 2005 - Based on publicly available data. Bars represent fiscal quarters. Organizations Subscribers 30,000 650,000 March 2007 Organizations Subscribers 20,000 350,000 October 2005
  • 21. Scalability and Performance Average Response Time (milliseconds) Transactions per quarter (millions) - Based on publicly available data. Points represent fiscal quarters.
  • 22. Talk Outline
    • Web 2.0 and Consumer Services
    • Enterprise Software as a Service
    • Case Study: salesforce.com
    • Database Virtualization
  • 23. High-Level Goals
    • Consolidate multiple businesses (tenants) onto the same operational system
    • Reduce total cost of ownership
      • Pooling resources
      • Improving management efficiency
    • Support Web 2.0 style collaboration
    • To the extent possible, hide multi-tenancy from developers and system administrators
  • 24. Specific Requirements
    • Pool database resources to improve their utilization
      • Avoid provisioning each tenant for their maximum load
      • Breaks down isolation: weakens security, increases resource contention, interferes with optimizations
    • Provide a tenant-aware administrative framework
      • Manage farms of individual multi-tenant databases
      • Support DML and DDL operations across tenants
      • Support tenant migration within and across farms
    • Support Web 2.0 style collaboration
      • Allow shared extensions to the base schema
      • Allow shared public data with private updates
    3 2
  • 25. Multi-Mode Delivery
    • Three ways of delivering software to the enterprise
      • On-premises The business controls the application
      • Hosted The service provider controls the application
      • Hybrid The application runs in the data center of the business in an appliance and is remotely administered by the service provider
    • Customers should be able to migrate between them
      • Or keep a warm back-up that is ready to use
    • Sweet spot is open source software, since that is commonly used in the hosted and hybrid models
  • 26. Consolidation Options
    • Shared Machine
    • Shared Process
    • Shared Table
    Isolation Resource Pooling
  • 27. Shared Machine
    • Cannot scale beyond tens of tenants per server
    • Appropriate for applications with a smaller number of larger tenants, e.g., for banking
    Memory requirements for a database with one empty CRM schema instance 273 MB 74 MB 171 MB 80 MB 55 MB COTS 3 COTS 2 COTS 1 MaxDB PostgresSQL
  • 28. Shared Process
    • Scalability limited due to the amount of metadata
      • But it is redundant for the base schema
    • Should scale up to thousands of tenants
    • If each tenant gets their own table space then migration entails simply moving files
    Memory requirements for a database with 10,000 empty CRM schema instances * extrapolated 359 MB 2061 MB 616 MB * 80 MB 79 MB * COTS 3 COTS 2 COTS 1 MaxDB PostgresSQL
  • 29. Shared Table
    • Data from many tenants in the same tables
      • Add a tenant id column
      • Tenant queries must fix the value for this column
    • Extend the base schema using generic columns
      • May be varchar or a mix of types
      • The database must compactly represent sparse tables
    Account 0021 0029 Name Acme Ball ... TenId 1041 1041 1053 1053 0016 0049 Gump Wonk Val0 1/3/95 3/7/72 red blue Val1 ---- ---- 35 18 ... Val100 ---- ---- ---- ----
  • 30. Shared Table
    • The Good News - Everything is pooled
      • Processes, memory, connections, prepared statements
      • Easy DML and DDL operations across tenants
      • Add, remove, and extend tenants with DML (not DDL)
    • The Bad News - Isolation is very weak
      • Irrelevant data infects query processing
        • Optimization Statistics
        • Table Scans
        • Data locality
      • No indexes or integrity constraints on generic columns
      • Migration requires querying the operational system
  • 31. Possible Improvements
    • Shared Process – increase resource pooling
      • Keep one copy of the meta-data about the base schema
      • Allow prepared statements over table names
      • Allow queries over table names
      • Dynamically set the principal for a database connection
    • Shared Table – increase isolation
      • Take the tenant ID into account in query optimization, indexing, and data placement
      • Could be done from inside the database or from outside in a SQL transformation layer
  • 32. Our Current Research
    • Adapt an open source database for multi-tenancy
    • Measure its scalability and performance using a benchmark for multi-tenant databases
    Lead Campaign Line Item Product Case Contact Contract Account Opportunity Asset conversion source source parent reports to signed by Simple CRM Schema