Zero Effort Multi-Tenancy
One of the larger (and most talked about!) hurdles of SaaS is building your application to be single instance, multi-tenant. Why is this important? Because single instance, multi-tenant applications prove to be the most cost effective types of SaaS applications but are also the most difficult to develop - at least before SaaSGrid came into the picture. When a SaaSGrid application is created, it is written very much like a regular on-premises application in that it targets single customer deployment with no notion of multi-tenancy in the source code, database, or user interfaces. However, once that SaaSGrid application is deployed to an instance of SaaSGrid and is running live, SaaSGrid automatically endows your application with a single instance, multi-tenant architecture with zero effort on your part.
SaaSGrid's zero effort multi-tenancy isolates your customers by handling data partitioning, request routing, and authorization security at the application server layer - even though your customers might be sharing resources. Moreover, SaaSGrid gives you the ability to define certain aspects of your application's multi-tenant behavior, such as whether data from multiple customers can be mixed in database deployments or should instead each be provided a dedicated database. This powerful concept of configurable "drop-in" single instance, multi-tenant capability provides a massive time-to-market boost and takes a major maintenance and security painpoint off your plate.
When writing your application to deploy with SaaSGrid, you don't need to worry about multi-tenancy. You can easily develop and test your code locally using the SaaSGrid SDK, and when ready can experience your application in a multi-tenant fashion by publishing it to a SaaSGrid instance. Once deployed, SaaSGrid will automatically provide login capabilities, tenant provisioning, and all other multi-tenant must haves, allowing you to focus on your business and its success - NOT the difficulties of SaaS delivery.
Related Media
