Features of a Multi-Tenant Cloud-based SaaS App
Multi-Tenant Data Access Security :
Cross-Organization and Cross-Application SSO

e.g. Single sign-on for the cloud and SaaS – OneLogin

Multi-Tenant Data Compliance :
 Satisfy Data Compliance and Regulations and Data Encryption
Multi-Tenant Data Acquisition :
Multi-Tenant Data Acquisition , MDM, Data Cleansing, Data Mapping – Component :
Capture data from Multiple Apps for Multiple Tenants through the same ‘Integration Platform’
“If it’s Not Multitenant, it’s Not Really SaaS.” —
Multi-Tenant Data Storage :
 > ‘Shared-Database Shared-Schema is the best approach for  ‘Tenants with low or moderate storage of data’
Here are few properties of the multi-tenant system using shared schema :
1. Data Splitting / Data Shading is Must (tenant based horizontal partitioning)  – Scalability
2. Break the structure of an entity into many Key-Value sub-structures.     – Extensibility
3. We should avoid application-level caching as much as possible (as there will be millions of rows per table) ; rather use Cold Cache.  – Speed & Memory
4. We should be able to support ‘custom attributes’ for one entity of a tenant without breaking the same entity of another tenant.   – SaaS Enablement
6. Infrequent, periodic or scheduled import of third party data through event queue  — Asynchrony
Immutable Staging DataStore  (sharded by User/Entity Keys) with ordered contextual entities with strong consistencies.
Analytics  Datastore (In-memory Spark Columnar store) with fast aggregation capability for low-latency data exploration .
Multi-Tenant Metadata Manager and Application Provisioning
Multi-Tenant Data Analysis :
Extensible Rules and Queries – configurable across tenants.
Tenant-Aware Resource Access Rules
Multi-Tenant Data Service API:
Tenant-aware Resource Access Rules.
Tenant-aware Server, Sessions and Cache.
Tenant-aware Rest Services , Work-flow and Rules-Engine
Multi-Tenant Data Apps Server : (Cloud-enabled and Tenant-aware )
 Application Resource Allocation (App Server / DB Connection / Fail-over ) for all the tenants without stepping into each other’s resources.
POD System is a popular recommended Multi-Tenant Model
— PaaS script will automatically roll out new resources …  its a mini-combo of (app-server, db, vm for a logical group of tenants)
Multi-Tenant Data Viz :
Multi-Tenant Charts/Graphs and Configurable Dashboards.
Pentaho , YellowFin are some of the Commercial Offerings.
The best thing is to build personalized Ad-hoc Pages with Dynamic Data Exploration capabilities (following the trends set by Datameer / Platfora / Indices )