1. Architectural Impact of SaaS
Eric Nelson
Microsoft

2. Basic SaaS Maturity Model
5/14/2019 9:42 PM
Basic SaaS Maturity Model
1. ad-hoc /custom
2. configurable single tenant
4. configurable multi tenant (scalable)
3. configurable multi tenant
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Multi-Tenant Efficient
5/14/2019 9:42 PM
Three Headed Monster
Scaleable
Configurable
Multi-Tenant Efficient
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

4. multi-tenant data architectures
5/14/2019 9:42 PM
multi-tenant data architectures
20 mins left
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. business model (can I monetise?) architectural model (can I do it?)
5/14/2019 9:42 PM 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?)
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. separate database per tenant
MGB 2003
5/14/2019 9:42 PM
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 6
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2003 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

7. same database, separate schema
MGB 2003
5/14/2019 9:42 PM
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 7
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2003 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8. same database, same schema
MGB 2003
5/14/2019 9:42 PM
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 8
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2003 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

9. single instance, mult-tenant
5/14/2019 9:42 PM
single instance, mult-tenant
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Configurable 5/14/2019 9:42 PM 20 mins left
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. … other domain specific considerations…
5/14/2019 9:42 PM
meta-data
UI/branding
workflow and rules
data model extensions
access control
… other domain specific considerations… 10
considerations
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. meta-data
UI/branding

13. meta-data
workflow/rules

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