Building a SaaS Application One of the 7 Keys to Success: Multi-Tenancy Mike Ormerod Architect, SaaS & Cloud Computing Strategy Progress Software Session. - презентация

1 Building a SaaS Application One of the 7 Keys to Success: Multi-Tenancy Mike Ormerod Architect, SaaS & Cloud Computing Strategy Progress Software Session 104

2 © 2009 Progress Software Corporation. All rights reserved. 2 7 Keys To Success Going from 1 to N Multi-tenancy Ensuring that data and applications are accessed only by those who need to know Security & Compliance Being able to easily use the UI technologies that meet the needs of the customer User Interface Flexibility Ensuring the application looks as the tenant and end-user want Personalization Ability to easily integrate to any other application by supporting all relevant standards Integration Always available and scales to any size Operational Excellence Provide a highly productive environment focused on OpenEdge and industry best practices Productivity

3 © 2009 Progress Software Corporation. All rights reserved. 3 7 Keys To Success Multi-tenancy Ensuring that data and applications are accessed only by those who need to know Security & Compliance Being able to easily use the UI technologies that meet the needs of the customer User Interface Flexibility Ensuring the application looks as the tenant and end-user want Personalization Ability to easily integrate to any other application by supporting all relevant standards Integration Always available and scales to any size Operational Excellence Provide a highly productive environment focused on OpenEdge and industry best practices Productivity Going from 1 to N

4 © 2009 Progress Software Corporation. All rights reserved. 4 IsolatingSharing Better economy of scale Simpler management Target like-customers Least cost to serve Easier customization, security Simpler throttling control Target dissimilar customers No transformation Tenant2Tenant3 App DB Infra. Tenant1 Isolated Tenancy Tenant1Tenant2Tenant3 App DB Infrastructure Shared Tenancy Tenant1Tenant2Tenant3 App DB Infrastructure Infrastructure Tenancy Tenant1Tenant2Tenant3 DB Infrastructure App Application Tenancy Multi-tenancy Options Continuum

5 © 2009 Progress Software Corporation. All rights reserved. Isolated Tenancy ApplicationIsolated DatabaseIsolated InfrastructureIsolated Tenant2Tenant3 App DB Infrastructure Tenant1 What is it? 5

6 © 2009 Progress Software Corporation. All rights reserved. Infrastructure Infrastructure Tenancy What is it? ApplicationIsolated DatabaseIsolated InfrastructureShared 6 Tenant2Tenant3 App DB Tenant1

7 © 2009 Progress Software Corporation. All rights reserved. Tenancy Through physical isolation. Separate hosts Virtualization Pathnames and naming Isolated & Infrastructure Tenancy Implementation 7 No change. Infrastructure provides physical separation Versions can be different Tenant-aware naming resolves naming conflicts Servers (AppServer, WebSpeed) naming e.g. servicename No change. Infrastructure provides physical separation Tenant-aware naming resolves naming conflicts e.g. dbname Host per tenant Shared host: Citrix / Terminal Services partition per tenant Virtual environment / software appliance per tenant Application Database Infrastructure

8 © 2009 Progress Software Corporation. All rights reserved. Tenant1Tenant2Tenant3 DB Infrastructure App Application Tenancy ApplicationShared DatabaseIsolated InfrastructureShared What is it? 8

9 © 2009 Progress Software Corporation. All rights reserved. Through TenantID and Isolated Databases: TenantID-DBname value pairs Stored in Tenancy Registry Flows through all layers of application Authentication maps end-user to TenantID Business objects activation Database tenancy through TenantID-DBname value-pairs Encryption Single instance. Multitenancy by setting and using TenantID throughout all application layers, and database tenancy through TenantID-DBname value-pairs TenantID+UserID to handle UserID duplicates across tenants Encryption key by tenant Tenancy Application Application Tenancy Implementation 9

10 © 2009 Progress Software Corporation. All rights reserved. Application Tenancy Implementation 10 Isolated by tenant. Tenancy through DB naming model: e.g. /db, dbsfolder/ db,… Tables do not need TenantID field No need for SQL Views for ODBC/JDBC Everything Shared: CPUs, RAM, HD, Communications, Web servers, etc Database Infrastructure

11 © 2009 Progress Software Corporation. All rights reserved. Tenant1Tenant2Tenant3 App DB Infrastructure Shared Tenancy ApplicationShared DatabaseShared InfrastructureShared What is it? 11

12 © 2009 Progress Software Corporation. All rights reserved. Shared Tenancy Implementation 12 Through TenantID Stored in Tenancy Registry Flows through all layers of application Authentication maps end-user to TenantID Business objects activation Data access (ABL and SQL) Encryption Single instance. Multitenancy by setting and using TenantID throughout all application layers TenantID+UserID to handle UserID duplicates across tenants Database CRUD always includes TenantID ODBC/JDBC access through SQL Views setting TenantID Encryption key by tenant Tenancy Application

13 © 2009 Progress Software Corporation. All rights reserved. Shared Tenancy Implementation TenantIDCustNumName 11John Smith 21Jane Doe 12Ludovic Eiffel 22Ingrid Schnabel ……… 13 Single instance Tables include TenantID field. Indices. Use TenantID for CRUD May want to consider SQL Views for Reporting and BI Everything Shared: CPUs, RAM, HD, Communications, Web servers, etc Database Infrastructure

14 © 2009 Progress Software Corporation. All rights reserved. When to Consider Isolated TenancyInfrastructure Tenancy Application Tenancy Shared Tenancy Time to market Short LongLongest Infrastructure costs High Low Economies of scale Very poorPoorHighHighest Scalability Poor HighHighest Provisioning Difficult EasyEasiest Admin/Mgmt costs Very highHighLowLowest Target type of tenants Dissimilar Similar Multitenant App Transformation No Yes (except DBs) Yes Coding difficulty Easy Less difficultDifficult Implement SLAs EasierEasyLess difficultDifficult Containment EasierEasyLess difficultDifficult 14

15 © 2009 Progress Software Corporation. All rights reserved. OpenEdge Platform Support Support for major virtualization platforms, e.g. VMWare, Citrix, HP, IBM, Windows, Solaris Modern ABL Dynamic Programming Class Based Standards Based OpenEdge RDBMS Low cost easy administration whether 1 db or 100s Tables per database and data per table effectively unlimited OpenEdge AppServer 15

16 © 2009 Progress Software Corporation. All rights reserved. OpenEdge – The Complete SaaS Platform 16 Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & ComplianceIntegrationTenant ManagementPersonalization & Customization

17 © 2009 Progress Software Corporation. All rights reserved. OpenEdge – The Complete SaaS Platform 17 OpenEdge Application Platform Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & ComplianceIntegrationTenant ManagementPersonalization & Customization

18 © 2009 Progress Software Corporation. All rights reserved. OpenEdge – The Complete SaaS Platform 18 OpenEdge Application Platform Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & ComplianceIntegrationTenant ManagementPersonalization & Customization Productivity/Operational Excellence

19 © 2009 Progress Software Corporation. All rights reserved. More Info Software as a Service Track Session 105: Operational Excellence Session 124: Tales from the Trenches: SaaS in Practice Architecture, SaaS & Cloud Community architecturehttp://communities.progress.com/pcom/community/psdn/openedge/ architecture 19

20 Building a SaaS Application One of the 7 Keys to Success: Multi-Tenancy Mike Ormerod Architect, SaaS & Cloud Computing Strategy Progress Software Session 104