Difference between virtualization and multi tenancy
Answers
Answered by
0
Very often SaaS application will scale better if it is designed from the ground up to take care of multi-tenancy issues such as application customization and data security isolation, and adhering to the principle of minimizing hard-binding of runtime computing resources to specific tenants. However, re-implementing an application completely is not always a viable option for the SaaS ISV initially, perhaps because of time-to-market restrictions or because there is a need to quickly prove that the SaaS market demand exist without investing too much in re-engineering effort. In some of these situations, virtualization technology can help address multi-tenancy concerns to a certain degree.
In addition to SaaS ISVs, multi-tenancy issues also impact SaaS hosters who are hosting ISV applications. Resources in the hosting environment must be efficiently partitioned and shared among the hosted ISV tenants, while simultaneously respect the performance and security isolation boundaries set between different applications. Here again, virtualization technology can help address some of the multi-tenancy needs that SaaS hosters have.
To date, there are many types of products and solutions that claim to offer virtualization capabilities, with more than a few promising quick routes to the on-demand software delivery market. It is important to know that not all virtualization solutions are created equal. Although most virtualization products can play a part in delivering SaaS, it is critical that the right kind of virtualization technology is used to address the appropriate multi-tenancy issue.
The figure below is an attempt to classify the kinds of strategies and virtualization patterns for addressing multi-tenancy concerns. At a high level, there are three buckets of multi-tenancy strategies:
- Physical Separation. Physical separation relies on giving each tenant his own dedicated hardware resources. For example, assigning separate physical servers to different tenants, or in some extreme cases, a significant section of data center to a large client.
- Virtualization. Virtualization is about using software to create application hosting environments that provide logical boundaries between each tenant. We will take a further look at the various virtualization techniques shortly.
- Design the application to be multi-tenant aware. The third strategy is to design different aspects of the application to automatically adjust its behavior differently for different tenants at runtime. This has been the main focus of most of my work on SaaS architecture guidance, which is to provide ISVs with best practices so that multi-tenancy is a first class consideration in application design.
In addition to SaaS ISVs, multi-tenancy issues also impact SaaS hosters who are hosting ISV applications. Resources in the hosting environment must be efficiently partitioned and shared among the hosted ISV tenants, while simultaneously respect the performance and security isolation boundaries set between different applications. Here again, virtualization technology can help address some of the multi-tenancy needs that SaaS hosters have.
To date, there are many types of products and solutions that claim to offer virtualization capabilities, with more than a few promising quick routes to the on-demand software delivery market. It is important to know that not all virtualization solutions are created equal. Although most virtualization products can play a part in delivering SaaS, it is critical that the right kind of virtualization technology is used to address the appropriate multi-tenancy issue.
The figure below is an attempt to classify the kinds of strategies and virtualization patterns for addressing multi-tenancy concerns. At a high level, there are three buckets of multi-tenancy strategies:
- Physical Separation. Physical separation relies on giving each tenant his own dedicated hardware resources. For example, assigning separate physical servers to different tenants, or in some extreme cases, a significant section of data center to a large client.
- Virtualization. Virtualization is about using software to create application hosting environments that provide logical boundaries between each tenant. We will take a further look at the various virtualization techniques shortly.
- Design the application to be multi-tenant aware. The third strategy is to design different aspects of the application to automatically adjust its behavior differently for different tenants at runtime. This has been the main focus of most of my work on SaaS architecture guidance, which is to provide ISVs with best practices so that multi-tenancy is a first class consideration in application design.
Answered by
0
In a 'multitenancy atmosphere', multiple customers share constant applications, within the same 'operational atmosphere', on 'constant hardware', with a constant storage mechanism. In 'virtualization', each application runs on a separate 'virtual machine' with its own OS.
- 'Virtualization' is creating 'several virtual servers' as per 'requirements' and needs using the same 'hardware infrastructure'. If we put it in a layered 'architecture layer 1' would be 'SAN' '(storage area network)', layer 2 would be 'hardware servers' ('blade servers') for 'resource allocation' and the top layer would be host servers for virtualization software like 'Citrix', 'VMware's vSphere', 'Xen', 'Microsoft Hyper V', 'Sun xvm' host server will run on the top level server which operating system the host server runs and virtual server can be based on which 'operating system'.
- 'Multitenancy' may be a kind of 'software package design' wherever one 'software package' instance will serve multiple distinct user teams. It means multiple customers of 'cloud vendor' area units victim the same 'computing resources'. As they're sharing the same 'computing resources' however the information of every 'Cloud client' is unbroken completely 'separate and secure'.
#SPJ3
Similar questions
English,
7 months ago