Multi-tenancy In the Cloud

1,777 views

Published on

How SwiftKnowledge supports the major multi-tenancy, multi-tier models in the cloud.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,777
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Each client can have its own virtual directory with branding and globalization customizations specific to their own requirements
  • External to Swift Assumptions: Data structures across clients are the same Automation of ETL and Cube repopulation is in place to satisfy “freshness” requirements of data in reports External to Swift Step 4 assumes that Client’s Branding and Localization has been completed via the corresponding xml files, and can then just be “dropped” into place during this step. This can also be automated. Can be automated for bulk user import into SwiftKnowledge users & groups Can be automated for efficiency in configuring large #’s of users
  • External to Swift Can be automated for bulk user import into SwiftKnowledge users & groups Can be automated for efficiency in configuring large #’s of users Step 1 above assumes: Data structures across clients are the same Automation of ETL and Cube repopulation is in place to satisfy “freshness” requirements of data in reports
  • External to Swift Can be automated for bulk user import into SwiftKnowledge users & groups Can be automated for efficiency in configuring large #’s of users Step 1 above assumes: Data structures across clients are the same Automation of ETL and Cube repopulation is in place to satisfy “freshness” requirements of data in reports
  • External to Swift Step 2 assumes that Client’s Branding and Localization has been completed via the corresponding xml files, and can then just be “dropped” into place during this step. This can also be automated. Can be automated for bulk user import into SwiftKnowledge users & groups Can be automated for efficiency in configuring large #’s of users Step 1 above assumes: Data structures across clients are the same Automation of ETL and Cube repopulation is in place to satisfy “freshness” requirements of data in reports
  • Multi-tenancy In the Cloud

    1. 1. WEBINAR Multi-Tenant Business Intelligence in a Cloud Computing Environment Allie Gentry, Chief Technology Officer Scott deVillers, Solution Architect February 18, 2010
    2. 2. Business Intelligence Trends <ul><li>For enterprises </li></ul><ul><ul><li>Increased BI adoption among business managers </li></ul></ul><ul><ul><li>Driven by improved usability and ease of use of ad-hoc query and reporting capabilities </li></ul></ul><ul><li>For ISVs and SaaS vendor applications </li></ul><ul><ul><li>BI is becoming an embedded component of ISV and SaaS vendor applications </li></ul></ul><ul><ul><li>ISVs and SaaS vendors need to deliver BI in context to the applications and the business </li></ul></ul><ul><li>For information aggregators </li></ul><ul><ul><li>Enterprises and information aggregators can productize valuable data through packaging it with web-based BI </li></ul></ul>Broad-based adoption of BI requires integrating data from multiple sources, both inside and outside the corporate firewall.
    3. 3. What is Multi-Tenancy? <ul><li>Definition </li></ul><ul><ul><li>A single instance of software runs on a server, serving multiple client organizations (tenants) </li></ul></ul><ul><li>How it works </li></ul><ul><ul><li>With a multi-tenant architecture, a software application is designed to virtually partition its data and configuration, so each client organization works with a customized virtual application instance </li></ul></ul><ul><li>Critical considerations for multi-tenancy </li></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Re-branding </li></ul></ul><ul><ul><li>Localization </li></ul></ul><ul><ul><li>Support for cloud computing-based deployments </li></ul></ul>
    4. 4. Use Cases for Multi-Tenant BI <ul><li>ISVs who want to offer hosted or SaaS solutions </li></ul><ul><li>Pure-play SaaS vendors </li></ul><ul><li>Enterprises deploying a solution globally across different groups/regions </li></ul><ul><li>Information aggregators seeking to offer access to data via web-based BI tools </li></ul>
    5. 5. Today’s Agenda <ul><li>The benefits of a multi-tenant approach to BI implementations in a cloud computing environment </li></ul><ul><li>How to add capacity as you add clients </li></ul><ul><li>How to easily overcome the data security concerns and challenges often associated with a multi-tenant approach </li></ul><ul><li>The characteristics and benefits behind the four main approaches to multi-tenant BI in a cloud computing environment, and which one is right for you </li></ul>
    6. 6. Benefits of Multi-Tenant BI <ul><li>Increased efficiencies and cost savings </li></ul><ul><ul><li>Leveraging a single installation of the BI application to support multiple clients provides for a lower cost of acquisition and ownership </li></ul></ul><ul><ul><li>Operational efficiencies allow rapid onboarding of new clients, time to productivity and revenue </li></ul></ul><ul><ul><li>Provides lower user license expenses </li></ul></ul><ul><li>Simplified user and release management </li></ul><ul><ul><li>Zero-footprint, web-based solutions require zero management at the client level </li></ul></ul><ul><ul><ul><li>No client-based license keys </li></ul></ul></ul><ul><ul><li>Simplified release management processes </li></ul></ul><ul><li>Increased responsiveness </li></ul><ul><ul><li>To both market changes and customer needs </li></ul></ul><ul><li>Easy re-branding </li></ul><ul><ul><li>Provides a personalized end user experience </li></ul></ul>
    7. 7. Architecture – Technical Details Interface Layer (Client Side) Ext JS HTML/CSS Presentation Layer (Server Side) jQuery Admin UI Reporting UI Portal Administration Base SwiftView Login Menus Admin Maps Grid Chart Meters Reporting Base Shared Components Security Layer Business Layer Admin Logic Reporting Logic Portal Administration Base SwiftView Login Menus Admin Variables Filtering Calculations Security Relation Rprt. Base Shared Components App Data Data Layer Data Mining Layer SwiftKnowledge Application Layer Users Groups Roles View Detail Query Analysis OLAP Database Layer Data Access Logic Metadata Cache Metadata Access Logic Data Access Relational Database Layer Data Access Data Access Logic Data Sources SQL ADO.NET/LINQ SQL ADOMD/ADOMD.NET SQL ADO.NET Oracle ADO.NET OLAP Rprt. Base Custom Data API MySQL ADO.NET Custom Database ADO.NET Client Browser Layer Web Application Layer Client Data Layer
    8. 8. Multi-Tenancy – Four Approaches SWIFTKNOWLEDGE SUPPORTS EVERY DELIVERY OPTION 1 1 Many Many 1 2 3 4 Web Application Layer Client Data Layer
    9. 9. Tenancy Approach | 1 : 1 <ul><li>Isolation at the data layer is logical and managed with SwiftKnowledge Component-Level Security </li></ul><ul><li>Uniform brand identity across clients </li></ul><ul><li>Application and data management can be delegated to client </li></ul><ul><li>Granularity of data security to specific clients and users </li></ul><ul><li>Data volume growth requirements are a factor of all tenants </li></ul>1
    10. 10. Tenancy Approach Steps to Onboard a New Client <ul><li>STEP 1: </li></ul><ul><li>Load new client data into existing database </li></ul><ul><li>STEP 2: </li></ul><ul><li>Import users for new client </li></ul><ul><ul><li>Source can be ADS, LDAP or custom third-party authentication </li></ul></ul><ul><ul><li>Users and groups are created on-the-fly </li></ul></ul><ul><li>STEP 3: </li></ul><ul><li>Define security at data layer for new client/users </li></ul>1
    11. 11. Tenancy Approach | 1 : Many <ul><li>Uniform brand identity across clients </li></ul><ul><li>Granularity of data security to specific clients and users </li></ul><ul><li>Data volume and growth requirements handled independently </li></ul>2
    12. 12. Tenancy Approach Steps to Onboard a New Client <ul><li>STEP 1: </li></ul><ul><li>Instantiate new hardware and populate database </li></ul><ul><li>STEP 2: </li></ul><ul><li>Import users for new client </li></ul><ul><ul><li>Source can be ADS, LDAP or custom third-party authentication </li></ul></ul><ul><ul><li>Users and groups are created on-the-fly </li></ul></ul><ul><li>STEP 3: </li></ul><ul><li>Define security at data layer for new client/users </li></ul>2
    13. 13. Tenancy Approach | Many : 1 <ul><li>Isolation at the data layer is logical and managed with SwiftKnowledge Component-Level Security </li></ul><ul><li>Unique branding and globalization </li></ul><ul><li>Application and data management can be delegated to client </li></ul><ul><li>Granularity of data security to specific clients and users </li></ul><ul><li>Data volume growth requirements are a factor of all tenants </li></ul>3
    14. 14. Tenancy Approach Steps to Onboard a New Client <ul><li>STEP 1: </li></ul><ul><li>Load new client data into existing database </li></ul><ul><li>STEP 2: </li></ul><ul><li>Create new virtual directory for new client </li></ul><ul><li>STEP 3: </li></ul><ul><li>Import users for new client </li></ul><ul><ul><li>Source can be ADS, LDAP or custom third-party authentication </li></ul></ul><ul><ul><li>Users and groups are created on-the-fly </li></ul></ul><ul><li>STEP 4: </li></ul><ul><li>Define security at data layer for new client/users </li></ul>3
    15. 15. Tenancy Approach | Many : Many <ul><li>Isolation is physical for all layers </li></ul><ul><li>Granularity of data security to specific clients and users </li></ul><ul><li>Flexibility to manage growth and administration </li></ul><ul><li>Branding and globalization unique </li></ul><ul><li>Client data volumes and growth handled independently </li></ul>Ideal for clients who require physical segregation of data; flexible growth path 4
    16. 16. Tenancy Approach Steps to Onboard a New Client <ul><li>STEP 1: </li></ul><ul><li>Instantiate new hardware </li></ul><ul><li>STEP 2: </li></ul><ul><li>Populate database with client-specific data </li></ul><ul><li>STEP 3: </li></ul><ul><li>Instantiate new web server </li></ul><ul><li>STEP 4: </li></ul><ul><li>Create new virtual directory for new client </li></ul><ul><li>STEP 5: </li></ul><ul><li>Import users for new client </li></ul><ul><ul><li>Source can be ADS, LDAP or custom third-party authentication </li></ul></ul><ul><ul><li>Users and groups are created on-the-fly </li></ul></ul><ul><li>STEP 6: </li></ul><ul><li>Define security at data layer for new client/users </li></ul>4
    17. 17. Steps for Client Onboarding Web Application Layer Instantiate new web server * Configure client-specific virtual directory Create application database Import users for new client Define security at data layer for new clients Secure application functionality, including administration Approach 1 / 1 1 / Many Many / 1 Many / Many * This can mean adding a virtual directory to an existing web server ** This can mean adding a new database to an existing database server Client Data Layer Instantiate new database server ** Populate database with client-specific data Load new client data into existing database 1 2 3 4
    18. 18. The Benefits of Each Approach Web App Layer/Data Layer Granularity of data security to specific clients and users Branding Globalization Client data volumes and growth handled independently Application/data management can be delegated to client Efficient cross-client comparisons Approach 1 / 1 1 / Many Many / 1 Many / Many 1 2 3 4
    19. 19. Considering a Multi-Tenancy Solution? <ul><li>Ask yourself </li></ul><ul><ul><li>What is my business strategy, and is it limited by my current technologies? </li></ul></ul><ul><ul><ul><li>The technology needs to support – not drive – the business strategy </li></ul></ul></ul><ul><li>Ask potential solution providers </li></ul><ul><ul><li>Does the solution support both cloud computing deployments and appliance installations? </li></ul></ul><ul><ul><li>Who will host the data? Are they certified for data security? </li></ul></ul><ul><li>Reference sites </li></ul><ul><ul><li>Microsoft </li></ul></ul><ul><ul><ul><li>http://msdn.microsoft.com/en-us/library/aa479086.aspx#mlttntda_topic2 </li></ul></ul></ul><ul><ul><li>Wikipedia </li></ul></ul><ul><ul><ul><li>http://en.wikipedia.org/wiki/Multitenancy </li></ul></ul></ul><ul><ul><ul><li>http://en.wikipedia.org/wiki/Multitenancy#Competitive_Differentiation </li></ul></ul></ul>
    20. 20. Unique Combination of Innovations For ISVs and SaaS <ul><li>Built specifically for ISVs and their end users </li></ul><ul><li>Uniquely satisfying end user experience </li></ul><ul><li>Ultra-fast BI performance in “Web time” </li></ul><ul><li>Linear scalability means lower data center costs </li></ul><ul><li>Flexible security and multi-tenancy </li></ul><ul><li>No plug-ins, client downloads, license keys </li></ul><ul><li>Completely re-brandable </li></ul><ul><li>Flexible licensing to fit any profit model </li></ul>Interactive Data Streaming ™ Component- Level Security ™ Zero-Footprint Web Deployment Breakthrough User Experience
    21. 21. Questions & Answers Submit questions using the Webex chat functionality found on the toolbar located in the lower right corner of your screen.
    22. 22. Thank You! Allie Gentry – [email_address] Scott deVillers – [email_address] www.swiftknowledge.com

    ×