1 / 16

Architectural Impact of SaaS

Architectural Impact of SaaS. Eric Nelson Microsoft. Basic SaaS Maturity Model. 1. ad-hoc /custom. 2. configurable single tenant. 4. configurable multi tenant (scalable). 3. configurable multi tenant. Three Headed Monster. Scaleable. Configurable. Multi-Tenant Efficient.

kenda
Download Presentation

Architectural Impact of SaaS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. 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 separate database per tenant 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 considerations UI/branding workflow and rules data model extensions access control … other domain specific considerations…

  12. meta-data UI/branding

  13. meta-data workflow/rules

  14. we want to track customer colour preferences we want to keep track of customer visits online our customers have peculiar address formats we need to track customer history by product 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...

More Related