Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System

2016 IEEE International Conference on Services Computing (SCC) Pub Date : 2016-09-01 DOI:10.1109/SCC.2016.56

L. Ochei, Andrei V. Petrovski, J. Bass

{"title":"Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System","authors":"L. Ochei, Andrei V. Petrovski, J. Bass","doi":"10.1109/SCC.2016.56","DOIUrl":null,"url":null,"abstract":"Implementing the required degree of isolation between tenants is one of the significant challenges for deploying a multitenant application on the cloud. In this paper, we applied COMITRE (COmponent-based approach to Multitenancy Isolation Through request RE-routing) to empirically evaluate the degree of isolation between tenants enabled by three multitenancy patterns (i.e., shared component, tenant-isolated component, and dedicated component) for a cloud-hosted Bug tracking system using Bugzilla. The study revealed among other things that a component deployed based on dedicated component offers the highest degree of isolation (especially for database transactions where support for locking is enabled). Tenant isolation based on performance (e.g., response time) favoured shared component (compared to resource consumption (e.g., CPU and memory) which favoured dedicated component). We also discuss key challenges and recommendations for implementing multitenancy for application components in cloud-hosted bug tracking systems with guarantees for isolation between multiple tenants.","PeriodicalId":115693,"journal":{"name":"2016 IEEE International Conference on Services Computing (SCC)","volume":"33 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2016-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2016 IEEE International Conference on Services Computing (SCC)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SCC.2016.56","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 7

Abstract

Implementing the required degree of isolation between tenants is one of the significant challenges for deploying a multitenant application on the cloud. In this paper, we applied COMITRE (COmponent-based approach to Multitenancy Isolation Through request RE-routing) to empirically evaluate the degree of isolation between tenants enabled by three multitenancy patterns (i.e., shared component, tenant-isolated component, and dedicated component) for a cloud-hosted Bug tracking system using Bugzilla. The study revealed among other things that a component deployed based on dedicated component offers the highest degree of isolation (especially for database transactions where support for locking is enabled). Tenant isolation based on performance (e.g., response time) favoured shared component (compared to resource consumption (e.g., CPU and memory) which favoured dedicated component). We also discuss key challenges and recommendations for implementing multitenancy for application components in cloud-hosted bug tracking systems with guarantees for isolation between multiple tenants.

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

实现所需程度的多租户隔离:云托管漏洞跟踪系统的案例研究

在租户之间实现所需的隔离程度是在云上部署多租户应用程序的重大挑战之一。在本文中，我们应用COMITRE(通过请求重路由实现多租户隔离的基于组件的方法)对使用Bugzilla的云托管Bug跟踪系统的三种多租户模式(即共享组件、租户隔离组件和专用组件)启用的租户之间的隔离程度进行了经验评估。该研究表明，基于专用组件部署的组件提供了最高程度的隔离(特别是对于启用了锁支持的数据库事务)。基于性能(例如，响应时间)的租户隔离倾向于共享组件(与倾向于专用组件的资源消耗(例如，CPU和内存)相比)。我们还讨论了在云托管的bug跟踪系统中为应用程序组件实现多租户的关键挑战和建议，并保证了多个租户之间的隔离。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文去求助

来源期刊

2016 IEEE International Conference on Services Computing (SCC)

自引率

0.00%

发文量