Multi-tenant databases for software as a service

Aulbach, Stefan; Grust, Torsten; Jacobs, Dean; Kemper, Alfons; Rittinger, Jan

doi:10.1145/1376616.1376736

Cited by 199 publications

(120 citation statements)

References 7 publications

Supporting

Mentioning

118

Contrasting

Unclassified

Order By: Relevance

“…, Jacobs and Aulbach (2007), and Aulbach et al (2008) give an overview on the separation of tenants on database level and validate their approaches.…”

Section: Related Workmentioning

confidence: 99%

Customizing Enterprise Software as a Service Applications: Back-End Extension in a Multi-tenancy Environment

Müller

Krüger

Enderlein

et al. 2009

Enterprise Information Systems

View full text Add to dashboard Cite

Abstract. Since the emerge of Salesforce.com, more and more business applications tend to move towards Software as a Service. In order to target Small and Medium-sized Enterprises, platform providers need to lower their operational costs and establish an ecosystem of partners, customizing their generic solution, to push their products into spot markets. This paper categorizes customization options, identifies cornerstones of a customizable, multi-tenancy aware infrastructure, proposes a framework that encapsulates multi-tenancy, and introduces a technique for partner back-end customizations with regard to a given real-world scenario.

show abstract

“…, Jacobs and Aulbach (2007), and Aulbach et al (2008) give an overview on the separation of tenants on database level and validate their approaches.…”

Section: Related Workmentioning

confidence: 99%

Customizing Enterprise Software as a Service Applications: Back-End Extension in a Multi-tenancy Environment

Müller

Krüger

Enderlein

et al. 2009

Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…Special security mechanisms, such as row level access control, are required to keep the tenant data isolated from each other. Backup procedures can be implemented efficiently by creating table spaces from shared tables for each tenant and making incremental backups [2], [4].…”

Section: ) Componentsmentioning

confidence: 99%

“…Different schema mapping techniques (i.e., layouts) for multi-tenant databases hosting the data of multiple clients are shown in an information view of the SPOSAD style in Fig. 4 (see also Aulbach et al [4]). The same data is shown for three different layouts.…”

Section: ) Componentsmentioning

confidence: 99%

“…Aulbach et al [4] provide a database centric view on multi-tenant architectures. They evaluate the performance properties of different flexible schemas for multi-tenant applications and propose a new, more efficient schema.…”

Section: Related Workmentioning

confidence: 99%

“…Existing attempts on providing a structured documentation of multi-tenancy architectural concepts either focus on restricted aspects (e.g., the database layer [4]) or depend on certain technologies (e.g., .NET [5], IBM/Java [6]). The documented architectures of existing multi-tenant systems (e.g., [3]) are difficult to transfer to other systems.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

The SPOSAD Architectural Style for Multi-tenant Software Applications

Koziolek

2011

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

Abstract-A multi-tenant software application is a special type of highly scalable, hosted software, in which the application and its infrastructure are shared among multiple tenants to save development and maintenance costs. The limited understanding of the underlying architectural concepts still prevents many software architects from designing such a system. Existing documentation on multi-tenant software architectures is either technology-specific or database-centric. A more technology-independent perspective is required to enable wide-spread adoption of multi-tenant architectures. We propose the SPOSAD architectural style, which describes the components, connectors, and data elements of a multi-tenant architecture as well as constraints imposed on these elements. This paper describes the benefits of a such an architecture and the trade-offs for the related design decisions. To evaluate our proposal, we illustrate how concepts of the style help to make current Platform-as-a-Service (PaaS) environments, such as Force.com, Windows Azure, and Google App Engine scalable and customizable.

show abstract