Building a SaaS Application: One of the keys to success: Multi-Tenancy

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

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

Multi-tenancy Options Continuum Isolating Sharing Better economy of scale Simpler management Target like-customers Least cost to serve Easier customization, security Simpler throttling control Target dissimilar customers No transformation Isolated Tenancy Shared Tenancy Infrastructure Tenancy Application Tenancy Tenant2 Tenant3 App App App DB DB DB Infra . Infra. Infra. Tenant1 Tenant1 Tenant2 Tenant3 App DB Infrastructure Tenant1 Tenant2 Tenant3 App App App DB DB DB Infrastructure Tenant1 Tenant2 Tenant3 DB DB DB Infrastructure App

Isolated Tenancy Tenant2 Tenant3 App App App DB DB DB Infrastructure Infrastructure Infrastructure Tenant1 What is it? Application Isolated Database Isolated Infrastructure Isolated

Infrastructure Tenancy Infrastructure What is it? Tenant2 Tenant3 App App App DB DB DB Tenant1 Application Isolated Database Isolated Infrastructure Shared

Isolated & Infrastructure Tenancy Tenancy Through physical isolation. Separate hosts Virtualization Pathnames and naming Implementation No change. Infrastructure provides physical separation Versions can be different Tenant-aware naming resolves naming conflicts Servers (AppServer, WebSpeed) naming e.g. <TenantID>servicename No change. Infrastructure provides physical separation Tenant-aware naming resolves naming conflicts e.g. <TenantID>dbname

Host per tenant

Shared host:

Citrix / Terminal Services “partition” per tenant

Virtual environment / software appliance per tenant

Application Database Infrastructure

Application Tenancy Tenant1 Tenant2 Tenant3 DB DB DB Infrastructure App What is it? Application Shared Database Isolated Infrastructure Shared

Application Tenancy

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 Implementation

Application Tenancy Implementation Isolated by tenant. Tenancy through DB naming model: e.g. <tenant1>/db, dbsfolder/<tenant1>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

Shared Tenancy Tenant1 Tenant2 Tenant3 App DB Infrastructure What is it? Application Shared Database Shared Infrastructure Shared

Shared Tenancy Implementation

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

Shared Tenancy Implementation 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 TenantID CustNum Name 1 1 John Smith 2 1 Jane Doe 1 2 Ludovic Eiffel 2 2 Ingrid Schnabel … … …

When to Consider Isolated Tenancy Infrastructure Tenancy Application Tenancy Shared Tenancy Time to market Short Short Long Longest Infrastructure costs High High Low Low Economies of scale Very poor Poor High Highest Scalability Poor Poor High Highest Provisioning Difficult Difficult Easy Easiest Admin/Mgmt costs Very high High Low Lowest Target type of tenants Dissimilar Dissimilar Similar Similar Multitenant App Transformation No No Yes (except DBs) Yes Coding difficulty Easy Easy Less difficult Difficult Implement SLAs Easier Easy Less difficult Difficult Containment Easier Easy Less difficult Difficult

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

OpenEdge – The Complete SaaS Platform Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & Compliance Integration Tenant Management Personalization & Customization

OpenEdge – The Complete SaaS Platform OpenEdge Application Platform Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & Compliance Integration Tenant Management Personalization & Customization

OpenEdge – The Complete SaaS Platform Productivity/Operational Excellence OpenEdge Application Platform Presentation Business Components Data Access Data Sources Enterprise Services Common Infrastructure Security & Compliance Integration Tenant Management Personalization & Customization

More Info

Software as a Service Track

Session 105: Operational Excellence

Session 124: Tales from the Trenches: SaaS in Practice

Architecture, SaaS & Cloud Community

http://communities.progress.com/pcom/community/psdn/openedge/architecture

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