Any single-tenant application that’s ported unchanged to a multi-tenant platform, no matter how much multi-tenancy is ‘injected’ into it, will not derive the full benefit of multi-tenancy until it has been rearchitected or written anew.
1. Customizability - If your application is not designed for customizability and configurability using a meta data based approach then emulation of multi-tenancy can make you technically ready for SaaS, but in the market place, are you going to force all your customers to use a standardised version of your product. What if each tenant wants the data model to be extended, forms and grids to be customized, or the notification templates to be custom designed.
2. Business rules and Workflows: If your existing application does not generalize and externalize the business rules and workflows out of your code base, you will not be able to support the diverse needs of different verticals and customer organizations using your product. The ability to customize the business rules and workflows at the tenant level is an important business need that you should architect for.
3. On the other hand, if you have architected your application for such extensive customization and configuration for each customer (from UI to datamodels to workflows), then even if you are not offering your product on the cloud, or if you are not offering it as a SaaS, you will still save a lot of money on implementation costs and maintenance costs. (As compared to maintaining a separate code base for each customer).
So a true multi-tenant architecture is not only about database sharing and data isolation, it is also about the ability of the application architecture to fulfill the diverse needs of multiple tenants / customers / user groups, by customizing and configuring data models, permissions, data scope policies, UI, rules, workflows etc. and still maintain a single code base.
In that sense whether or not an application needs a true multi-tenant architecture is as much a business decision as it is technical
1. Customizability - If your application is not designed for customizability and configurability using a meta data based approach then emulation of multi-tenancy can make you technically ready for SaaS, but in the market place, are you going to force all your customers to use a standardised version of your product. What if each tenant wants the data model to be extended, forms and grids to be customized, or the notification templates to be custom designed.
2. Business rules and Workflows: If your existing application does not generalize and externalize the business rules and workflows out of your code base, you will not be able to support the diverse needs of different verticals and customer organizations using your product. The ability to customize the business rules and workflows at the tenant level is an important business need that you should architect for.
3. On the other hand, if you have architected your application for such extensive customization and configuration for each customer (from UI to datamodels to workflows), then even if you are not offering your product on the cloud, or if you are not offering it as a SaaS, you will still save a lot of money on implementation costs and maintenance costs. (As compared to maintaining a separate code base for each customer).
So a true multi-tenant architecture is not only about database sharing and data isolation, it is also about the ability of the application architecture to fulfill the diverse needs of multiple tenants / customers / user groups, by customizing and configuring data models, permissions, data scope policies, UI, rules, workflows etc. and still maintain a single code base.
In that sense whether or not an application needs a true multi-tenant architecture is as much a business decision as it is technical
1 comment:
Hello,
Since this sort of hosting services helps to share resources, it reduces the overall cost of the company. Organizations also have freedom to allocate resources and demand for more bandwidth whenever required. Apart from this consistent performance and complete control over configurations are some other notable features which most companies would love to have.
Cloud Hosting India
Post a Comment