AA is responsible for defining rules and policies (stored in PRep) while considering multiple tenants, applications, data sharing and communication services.
In this paper, a multi-tenancy management framework is proposed to enable the jointly optimized design of quality-of-services (QoSs -aware virtualization and routing by tenant isolation and prioritization as well as flow allocation, fulfilling QoSs -awarements of tenants' applications.
When more people report, they can better evaluate future tenants' applications.
Recently, MTA has been extended to allow a tenant application to have its own sub-tenants, where the tenant application acts like a SaaS infrastructure.
Parts of a single tenant application can be shared or not shared.
Updating the code for a multi-tenant application means rolling out and testing a single instance of the application.
In STA, each tenant application needs not only to develop its own functionalities, but also to prepare an infrastructure to allow its sub-tenants to develop customized applications.
A single tenant application can be delivered from a virtualized server in the cloud or on a server inside your data center.
Therefore, the proposed model allows to define a unique infrastructure for a multi-tenant application platform that can serve multiple customers at the same time.
For instance, a vulnerability at a tenant application may result in the jeopardy of the whole service, as witnessed by the Amazon Zeus botnet incident.
