An Elastic Multi-tenant Database Schema for Software as a Service

Yaish, Haitham; Goyal, Madhu; Feuerlicht, George

doi:10.1109/dasc.2011.127

Cited by 18 publications

(24 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Pivot Tables" Technique is derived from the shared tables schema, it was explicated in [1]. This technique eliminates null values and supports more flexible extensions at the expense of increasing query processing time for inserting, updating and deleting operations.…”

Section: A Techniques Deploying a Single Approachmentioning

confidence: 99%

“…This technique was explicated in [5], and provides a high performance, however neglects the storage space and scalability. It was preferred to use when applications have a few tenants or a few tables [1].…”

Section: A Techniques Deploying a Single Approachmentioning

confidence: 99%

“…Therefore, a lot of software vendors turn to the principle of sharing hardware resources, software and services over the Internet among a large number of customers, this environment is called cloud computing, and its customers are called tenants. The cloud software delivery model is called Software as a Service (SaaS), and multi-tenancy is the primary characteristic of SaaS [1], as it allows SaaS vendors to run a single instance of an application and a database to serve multiple tenants with various requirements.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Hybrid Multi-Tenant Database Schema for Multi-Level Quality of Service

Saleh¹,

Fouad²,

Abu-Elkheir³

2014

ijacsa

View full text Add to dashboard Cite

Abstract-Software as a Service (SaaS) providers can serve hundreds of thousands of customers using sharable resources to reduce costs. Multi-tenancy architecture allows SaaS providers to run a single application and a database instance, which support multiple tenants with various business needs and priorities. Until now, the database management systems (DBMSs) have not had the notion of multi-tenancy, and they have not been equipped to handle customization or scalability requirements, that are typical in multi-tenant applications. The multi-tenant database performance should adapt to tenants workloads and fit their special requirements. In this paper, we propose a new multitenant database schema design approach, that adapts to multitenant application requirements, in addition to tenants needs of data security, isolation, queries performance and response time speed. Our proposed methodology provides a trade-off between the performance and the storage space. This proposal caters for the diversity in tenants via defining multi-level quality of service for the different types of tenants, depending on tenant rate and system rate. The proposal presents a new technique to distribute data in a multi-tenant database horizontally to a set of allotment tables using an isolation point, and vertically to a set of extension tables using a merger point. Finally, we present a prototype implementation of our method using a real-world case study, showing that the proposed solution can achieve high scalability and increase performance for tenants who need speedy performance and economize storage space for tenants who do not have demanding quality of service.

show abstract

Section: A Techniques Deploying a Single Approachmentioning

confidence: 99%

Section: A Techniques Deploying a Single Approachmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Hybrid Multi-Tenant Database Schema for Multi-Level Quality of Service

Saleh¹,

Fouad²,

Abu-Elkheir³

2014

ijacsa

View full text Add to dashboard Cite

show abstract

“…There are various models of multi-tenant database schema designs and techniques which have been studied and implemented to overcome multi-tenant database challenges [14]. Nevertheless, these techniques are still not overcoming multi-tenant database challenges [1].…”

Section: Introductionmentioning

confidence: 99%

“…The database design of EET technique is shown in the Appendix. This technique enables tenants creating and configuring their own virtual database schema including: the required number of tables and columns, the virtual database relationships for any of CTTs or VETs, and the suitable data types and constraints for a table columns during multi-tenant application run-time execution [14]. In this paper, we are proposing a multi-tenant database proxy service called Elastic Extension Tables Proxy Service (EETPS) to combine, generate, and execute tenants' queries by using a codebase solution that converts multi-tenant queries into a normal database queries.…”

Section: Introductionmentioning

confidence: 99%

Proxy Service for Multi-tenant Database Access

Yaish

Goyal

Feuerlicht

2013

Availability, Reliability, and Security in Information Systems and HCI

Self Cite

View full text Add to dashboard Cite

Abstract. The database of multi-tenant Software as a Service (SaaS) applications has challenges in designing and developing a relational database for multi-tenant applications. In addition, combining relational tables and virtual relational tables to make them work together and act as one database for each single tenant is a hard and complex problem to solve. Based on our multitenant Elastic Extension Tables (EET), we are proposing in this paper a multitenant database proxy service to combine multi-tenant relational tables and virtual relational tables, to make them act as one database for each single tenant. This combined database is suitable to run with multi-tenant SaaS single instance applications, which allow tenants designing their database and automatically configuring its behavior during application runtime execution. In addition, these applications allow retrieving tenants data by simply calling functions from this service which spare tenants from spending money and efforts on writing SQL queries and backend data management codes, and instead allowing them to focus on their business and to create their web, mobile, and desktop applications. The feasibility and effectiveness of the proposed service are verified by using experimental data on some of this service functions.

show abstract