Degrees of tenant isolation for cloud-hosted software services: a cross-case analysis.

Ochei, Laud Charles; Bass, Julian M.; Petrovski, Andrei

Abstract

A challenge, when implementing multi-tenancy in a cloud-hosted software service, is how to ensure that the performance and resource consumption of one tenant does not adversely affect other tenants. Software designers and architects must achieve an optimal degree of tenant isolation for their chosen application requirements. The objective of this research is to reveal the trade-offs, commonalities, and differences to be considered when implementing the required degree of tenant isolation. This research uses a cross-case analysis of selected open source cloud-hosted software engineering tools to empirically evaluate varying degrees of isolation between tenants. Our research reveals five commonalities across the case studies: disk space reduction, use of locking, low cloud resource consumption, customization and use of plug-in architecture, and choice of multi-tenancy pattern. Two of these common factors compromise tenant isolation. The degree of isolation is reduced when there is no strategy to reduce disk space and customization and plug-in architecture is not adopted. In contrast, the degree of isolation improves when careful consideration is given to how to handle a high workload, locking of data and processes is used to prevent clashes between multiple tenants and selection of appropriate multi-tenancy pattern. The research also revealed five case study differences: size of generated data, cloud resource consumption, sensitivity to workload changes, the effect of the software process, client latency and bandwidth, and type of software process. The degree of isolation is impaired, in our results, by the large size of generated data, high resource consumption by certain software processes, high or fluctuating workload, low client latency, and bandwidth when transferring multiple files between repositories. Additionally, this research provides a novel explanatory framework for (i) mapping tenant isolation to different software development processes, cloud resources and layers of the cloud stack; and (ii) explaining the different trade-offs to consider affecting tenant isolation (i.e. resource sharing, the number of users/requests, customizability, the size of generated data, the scope of control of the cloud application stack and business constraints) when implementing multi-tenant cloud-hosted software services. This research suggests that software architects have to pay attention to the trade-offs, commonalities, and differences we identify to achieve their degree of tenant isolation requirements.

Citation

OCHEI, L.C., BASS, J.M. and PETROVSKI, A. 2018. Degrees of tenant isolation for cloud-hosted software services: a cross-case analysis. Journal of cloud computing [online], 7, article ID 22. Available from: https://doi.org/10.1186/s13677-018-0121-8

• Journal Article Type: Article
• Acceptance Date: Oct 26, 2018
• Online Publication Date: Dec 17, 2018
• Publication Date: Dec 17, 2018
• Deposit Date: Nov 2, 2018
• Publicly Available Date: Dec 17, 2018
• Journal: Journal of cloud computing
• Electronic ISSN: 2192-113X
• Publisher: Springer
• Peer Reviewed: Peer Reviewed
• Volume: 7
• Article Number: 22
• DOI: https://doi.org/10.1186/s13677-018-0121-8
• Keywords: Multitenancy; Degree of isolation; Cloud patterns; Global software development; Software development tools; Cloud hosted software services; Application component; Case study research; Crosscase analysis
• Public URL: http://hdl.handle.net/10059/3206
• Contract Date: Nov 2, 2018