Architectural Impact of SaaS - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Architectural Impact of SaaS

Description:

UI/branding. workflow and rules. data model extensions. access control ... UI/branding. meta-data. workflow/rules. meta-data. data model extensions. meta-data ... – PowerPoint PPT presentation

Number of Views:248
Avg rating:3.0/5.0
Slides: 17
Provided by: EricN46
Category:

less

Transcript and Presenter's Notes

Title: Architectural Impact of SaaS


1
Architectural Impact of SaaS
  • Eric Nelson
  • Microsoft

2
Basic SaaS Maturity Model
1. ad-hoc /custom
2. configurable single tenant
4. configurable multi tenant (scalable)
3. configurable multi tenant
3
Three Headed Monster
Scaleable
Configurable

Multi-Tenant Efficient
4
  • multi-tenant data architectures

5
vs
share
isolate
business model (can I monetise?) architectural
model (can I do it?) operational model (can I
guarantee SLAs?) regulatory constraints (can we
share data?)
6
separate database per tenant
  • Approach
  • Meta data identifies database instance for each
    tenant
  • Advantages
  • Easy to implement data model extension
  • Easy to restore tenant data
  • More security isolation
  • Tradeoff
  • Number of tenants per database server is low
  • Higher management, backup cost and database
    server infrastructure costs
  • When to use
  • When tenant has specific database isolation
    requirements

Tenant A
Tenant B
Tenant C
7
same database, separate schema
  • Approach
  • Each tenant gets their own group of tables in the
    same database.
  • Advantages
  • Easy to implement data model extension
  • Moderate security isolation
  • Better tenant scale per server
  • Tradeoff
  • More difficult to restore tenant data
  • When to use
  • Number of tables for the app is small (100s)
  • Scale per server is important
  • OK to co-locate tenant data in same database

Tenant A
Tenant B
Tenant C
8
same database, same schema
  • Approach
  • All tenants use the same set of tables in the
    same database.
  • Advantages
  • Better tenant scale per server
  • Cost of management and backup is lower
  • Tradeoff
  • Difficult to restore tenant data
  • Harder to implement data model extension
  • When to use
  • Scale per server is important
  • OK to co-mingle tenant data in same database

Tenant B
Tenant A
Tenant C
9
  • single instance, mult-tenant

10
  • Configurable

11
meta-data
UI/branding workflow and rules data model
extensions access control other domain specific
considerations
  • considerations

12
meta-data
  • UI/branding

13
meta-data
  • workflow/rules

14
meta-data
  • data model extensions

15
meta-data
  • access control

16
Summary
  • Plenty of stuff to get right ?
  • Plenty of stuff to get wrong ?
  • It is not easy to do well...
Write a Comment
User Comments (0)
About PowerShow.com