7. Same situation applies to the cloud
based software applications.
In
SaaS (Software as a Service) Model
Most of the web applications are SaaS – But not
Multi-Tenant…!
Multi-Tenant Examples,
Highrise
Jira
YaY
In these systems, organizations make their
accounts and they are provided a look and feel
of their own „Home‟
8. Why this is so important?
Data is vital for some businesses.
Should be able to isolate data among
tenants in SaaS model.
If
we provide it…. We have Competitive
Advantage.
10. We can identify 3 different
architectures at present…
Separate DB – Separate Schema
Shared DB – Separate Schema
Shared DB – Shared Schema
11. Separate DB – Separate Schema
Extendibilitywith tenant specific requirements
Easy Backup
High Cost
Suitable for Medical and Banking applications in
spite of high cost
12. Shared DB – Separate Schema
Separate set of tables for each tenant in same
DB
Extendible and easy to implement
Suitable if No. of Tenants < 100
Low cost than the previous one
13. Shared DB – Shared Schema
Lowest Cost
Additional development effort
Less security
Each row contains tenant Id
Suitable for a huge cluster of tiny tenants
18. InYayCRM we have invented a model
that is supported all those architectures
You can,
- distribute databases in a server farm
- expand and shrink the number of
databases
- move tenants among databases
19. Metadata Tenant
Database Databases
Client Application
Server