Affiliation:
1. Worcester Polytechnic Institute, MA, USA
2. University of Massachusetts Amherst, Amherst, MA
Abstract
Online applications that serve global workload have become a norm and those applications are experiencing not only temporal but also spatial workload variations. In addition, more applications are hosting their backend tiers separately for benefits such as ease of management. To provision for such applications, traditional elasticity approaches that only consider temporal workload dynamics and assume well-provisioned backends are insufficient. Instead, in this article, we propose a new type of provisioning mechanisms—geo-elasticity, by utilizing distributed clouds with different locations. Centered on this idea, we build a system called DBScale that tracks geographic variations in the workload to dynamically provision database replicas at different cloud locations across the globe. Our geo-elastic provisioning approach comprises a regression-based model that infers database query workload from spatially distributed front-end workload, a two-node open queueing network model that estimates the capacity of databases serving both CPU and I/O-intensive query workloads and greedy algorithms for selecting best cloud locations based on latency and cost. We implement a prototype of our DBScale system on Amazon EC2’s distributed cloud. Our experiments with our prototype show up to a 66% improvement in response time when compared to local elasticity approaches.
Funder
National Science Foundation
Publisher
Association for Computing Machinery (ACM)
Subject
Software,Computer Science (miscellaneous),Control and Systems Engineering
Reference52 articles.
1. Consistency Tradeoffs in Modern Distributed Database System Design: CAP is Only Part of the Story
2. Amazon Global Infrastructure 2016. Amazon Global Infrastructure. Retrieved from http://aws.amazon.com/about-aws/global-infrastructure/. Amazon Global Infrastructure 2016. Amazon Global Infrastructure. Retrieved from http://aws.amazon.com/about-aws/global-infrastructure/.
3. Amazon Route 53 2015. Amazon Route 53: Choosing a Routing Policy. Retrieved from http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html. Amazon Route 53 2015. Amazon Route 53: Choosing a Routing Policy. Retrieved from http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html.
4. Internet Web servers: workload characterization and performance implications