By Topic

Strict SLAs for Operational Business Intelligence

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
Michael Seibold ; Dept. of Comput. Sci., Tech. Univ. Munchen, Garching, Germany ; Alfons Kemper ; Dean Jacobs

Today, SLAs for SaaS business applications usually lack stringent service level objectives and significant penalties. Moreover, Operational Business Intelligence features of modern business applications, like analytic dashboards, result in mixed workloads which make it even more difficult to predict execution times accurately due to resource contention. In contrast to the traditional three-tier architecture, an architecture for SaaS business applications should combine application and database layer to allow for processing business transactions and queries according to a queuing approach which enables strict SLAs with stringent response time and throughput guarantees. With stricter SLAs it would be easier to compare different cloud offerings with on-premise solutions and thus cloud computing could become more attractive for potential customers.

Published in:

Cloud Computing (CLOUD), 2011 IEEE International Conference on

Date of Conference:

4-9 July 2011