Abstract
A key challenge in porting enterprise software systems to the cloud is the migration of their database. Choosing a cloud provider and service option (e.g., a database-as-a-service or a manually configured set of virtual machines) typically requires the estimation of the cost and migration duration for each considered option. Many organisations also require this information for budgeting and planning purposes. Existing cloud migration research focuses on the software components, and therefore does not address this need. We introduce a two-stage approach which accurately estimates the migration cost, migration duration and cloud running costs of relational databases. The first stage of our approach obtains workload and structure models of the database to be migrated from database logs and the database schema. The second stage performs a discrete-event simulation using these models to obtain the cost and duration estimates. We implemented software tools that automate both stages of our approach. An extensive evaluation compares the estimates from our approach against results from real-world cloud database migrations.
Highlights
The benefits of hosting an enterprise system on the cloud — instead of on-premise physical servers — are well understood and documented [1]
The ARTIST [4] and REMICS [5] cloud migration methodologies refer to the database but do not support any database specific challenges
We present and assess the accuracy of the database migration cost and duration predictions produced by the approach, and its estimation of cloud database running costs in “Migration” and
Summary
The benefits of hosting an enterprise system on the cloud — instead of on-premise physical servers — are well understood and documented [1]. Some organisations have been using clouds for over a decade and are considering switching provider [2], while others are planning an initial migration [3]. The most challenging component to migrate is often the database due to the size and importance of the data it contains. The existing cloud migration work focuses on the software components and gives minimal consideration to data. The ARTIST [4] and REMICS [5] cloud migration methodologies refer to the database but do not support any database specific challenges. Cloud deployment simulators like CDOSim [6] focus only on compute resources. The limitations of these existing cloud migration methodologies are described further in “Related work” section
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
