Tuesday, August 7, 2012

Multi-tenant database requirements

The following is a partial wish list for a multi-tenant DBMS:
  • Distribute data across multiple nodes for scalability
  • Restrict user access by account/tenant
  • Backup multiple accounts/tenants at once
  • Restore data for a single account/tenant
  • Allow multiple schema versions
  • Maintain multiple replicas for durability
  • Meter and limit activities by account/tenant. NOTE: They should be measured in CPU cycles not in clock time (the query clock time limit as in SalesForce depends on the overall database load and adds unnecessary limitations)




No comments:

Post a Comment