Candy Crush is migrating to Google Cloud, marking its first major cloud migration as decided by the online game-maker, King. Starting in early 2019, Candy Crush will be hauling a substantial amount of big data from on-premise to Google Cloud Platform.
A cloud migration is no easy feat, and for a company that provides online gaming to over 270 million people globally, choosing the right cloud provider to navigate the challenges of such a move is crucial. Aside from “even richer online gaming experiences,” Sunil Rayan, managing director of gaming at Google Cloud, makes a good case for why Google was the best choice for Candy Crush:
“It will continue to innovate and demonstrate its leadership position as a global innovator by utilising our big data, AI and machine learning capabilities to give its engineers the next generation of tools to build great experiences.”
But with the potential for better gaming, higher speed, and scalability, a cloud migration also comes with a few big risks. Here are 3 things Candy Crush can do to make their cloud migration sweeter:
1. Don’t rush data transfer
Transferring data from on-premise to the cloud is a huge undertaking, especially for a company that claims to have the largest Hadoop cluster in Europe. Transferring massive amounts of data is not recommended because it slows download speed, so it would be best for Candy Crush to make the move in parts, over time, and with the anticipation of potentially massive transfer costs associated with moving data out of or into a cloud.
2. Prepare for potential downtime
Downtime is a huge risk for any application, let alone a game played by millions across the world. Candy Crush can’t afford for downtime on a game. Users say is downright addictive, so it’s important to account for inconsistencies in data, examine network connections, and prepare for the real possibility of applications going down during the cloud migration process.
3. Adapt to technologies for the new cloud
Since choosing a cloud provider means committing to a heavy amount of time reconfiguring an application for the move – it’s important to evaluate that the technology is the best fit. Technology is a big reason for Candy Crush moving their monolothic, on-premise environment to Google Cloud. Asa Bresin, FVP of technology at King, listed innovations in machine learning, query processing, and speed as drivers for cloud migration, and with technology known for speed and scalability, Google has met their requirements.
Bonus: Keep costs in check. Whether it’s heavy transfer costs, losing money during downtime periods, or the time and manpower needed to reconfigure an application to the cloud – cloud migrations come with costs. The time and costs of a cloud migration are easily misunderstood or drastically understated. For ease and efficiency of keeping costs in check throughout and after the migration process, it’s important to have an understanding of cloud service offerings, pricing models, and the complexity of a cloud adoption budget. Evaluate all of these costs and look into options that will help you save post-migration, likeoptimization tools.
With a gradual shift, planning for risks of downtime, and the patience and flexibility to reconfigure for Google Cloud, Candy Crush can win at cloud migration.
Today we have news that both Finance and DevOps folks will appreciate to improve cloud cost governance: ParkMyCloud and CloudHealth have taken our partnership a step further with a first-of-its-kind technical integration. Our products now work together to give you a seamless cloud management experience, with a single place to go for multi-cloud cost management, reporting, and governance. Our goal is to save you time and money, and to improve financial accountability and management processes.
Customers in software, biotechnology, and education have tried it out — and are saving an average of $25,000 per month on their cloud bills and the feedback has been great. They say it’s rare to find integrations between the major platforms they use throughout the day, and this setup is unique.
Melanie Metcalfe, Director of Project Support at Foster Moore, said, “what we need to manage and optimize our cloud environments is cost control, user governance, and detailed reporting. It makes our cloud operations simpler and easier when solutions from different vendors are integrated out of the box, and we’re glad to see CloudHealth and ParkMyCloud making this a reality.“
Here’s what a typical use case might look like if you’re a user of both products:
You log in to your CloudHealth account and take a quick look at your AWS dashboard.
You navigate to Pulse -> HealthCheck to find all possible optimizations in your environment.
On the list, you see ParkMyCloud, indicating that you have savings potential.
You click that to check out your list of EC2 instances, and find a few with a ParkMyCloud icon to show they’re recommended to park.
What does this mean? ParkMyCloud has analyzed your resource utilization patterns and automatically created an optimized on/off schedule that can save you money. You just need to apply it.
You click the ParkMyCloud icon, which takes you to your ParkMyCloud recommendations screen to take action. You can click to accept the parking schedule as is, or modify it (including the option to be more conservative or more aggressive.)
You go back to check out your CloudHealth reports, which include the data from your ParkMyCloud savings – all able to break down by environment, app, team, and more, for better visibility and cloud cost governance.
The integration is especially exciting as it continues the momentum in the multi-cloud management space kicked off by last week’s news that VMware will acquire CloudHealth to provide multi-cloud operations at a global scale — congrats to the whole team.
Learn more about the ParkMyCloud/CloudHealth integration and partnership on this page. Interested in seeing a demo of this cloud cost governance solution? Schedule a demo here.
ParkMyCloud, Leader in Automated Cost Optimization, and CloudHealth Technologies, Leader in Hybrid Cloud Governance, Integrate to Provide End-to-End Multi-Cloud Cost Control
September 6, 2018 (Dulles, VA) – ParkMyCloud, the leading enterprise platform for continuous cost control in public cloud, and CloudHealth Technologies, trusted cloud management platform provider, today announced that they have furthered their partnership with a technology integration that provides customers with end-to-end multi-cloud cost control and visibility.
More than $12.9 billion will be wasted on unused cloud resources this year – which means public cloud users have an immediate need for automated savings and governance. Customers leveraging ParkMyCloud and CloudHealth’s integrated solution are empowered to reduce this cloud waste – in fact, customers already using both platforms currently save an average of more than $25,000 monthly on their cloud bills.
Our joint customers experience a seamless, integrated solution, including:
ParkMyCloud’s SmartParkingTM recommendations to optimize resource on/off time, which can be actioned for savings in a matter of clicks, now manageable through the CloudHealth platform
CloudHealth’s recommendations to optimize public and private cloud resources with complete security
Analytics and reporting on spending and savings by environment, department, application, resource and more, providing visibility to make smarter business decisions.
“What we need to manage and optimize our cloud environments is cost control, user governance, and detailed reporting,” said Melanie Metcalfe, Director of Project Support at Foster Moore. “It makes our cloud operations simpler and easier when solutions from different vendors are integrated out of the box, and we’re glad to see CloudHealth and ParkMyCloud making this a reality.“
“We’re seeing a trend of more and more companies using multiple clouds,” said ParkMyCloud CEO Jay Chapel. “What single- and multi-cloud customers have in common are skyrocketing bills, and they don’t have the time or resources to control these costs. We solve this problem by providing an automated cost control solution. By combining this with CloudHealth’s visibility and governance, customers can achieve end-to-end cloud cost optimization and governance.”
This announcement continues the momentum in the multi-cloud management space kicked off by last week’s news that VMware will acquire CloudHealth to provide multi-cloud operations at a global scale.
ParkMyCloud is a SaaS platform that automatically identifies and eliminates public cloud resource waste, reducing spending by 65% or more — think “Nest for the cloud.” AWS, Azure, Google Cloud, and Alibaba Cloud users such as McDonald’s, Sysco, Unilever, Fox, and Sage Software have used ParkMyCloud to cut their cloud spending by millions of dollars annually. ParkMyCloud helps companies like these optimize and govern cloud usage by integrating cost control into their DevOps processes. For more information, visit https://www.parkmycloud.com.
CloudHealth Technologies provides the world’s most trusted software platform for accelerating business transformation in the cloud. More than 3,500 organizations globally rely on CloudHealth to manage over $5B in combined cloud spend, based on the platform’s ability to easily manage cost, ensure security compliance, improve governance and automate actions across multi-cloud environments. Known for offering the highest levels of data integrity throughout an organization’s entire cloud journey, CloudHealth is the platform of choice for leading enterprises and service providers, such as Pinterest, Yelp, Dow Jones, Zendesk, Skyscanner and SHI. With offices around the globe, the company is backed by Kleiner Perkins, Meritech, Sapphire Ventures, Scale Venture Partners, .406 Ventures and Sigma Prime Ventures.
The next plain on the cost optimization frontier for ParkMyCloud is cloud sizing. We have been working on product features around resource sizing that will deliver greater automation in the management of cloud infrastructure. A key part of this effort has involved analysis of cloud usage patterns across our entire user base. We’ve identified some interesting patterns and correlations in cloud sizing and usage.
vCPU Utilization Patterns: Lower than Expected
One data point that caught our attention was vCPU metric data, specifically the very low average (and peak) utilization we see in our users’ infrastructure. We know anecdotally that a large proportion of what users manage in our platform consists of non-production instances used for development, staging, testing, and data analytics workloads, many of which do not need to run 24/7/365. But even bearing this in mind, we see a surprisingly low vCPU utilization. Based on our most recent analysis of instances from across the four public cloud providers we support, some 50% of instances had an average vCPU of only 2% and a peak of 55%. Even at the 75th percentile, average utilization was only 7%, albeit with a peak of 98%.
What leads to these cloud sizing decisions?
Of course, when selecting instance sizes and types, vCPU is not the only consideration. To make an accurate assessment of the match between workload and instance type, there are several data points to consider, including memory, network, disk, etc. We have no visibility into the specific workloads on these instances and why they were chosen, but we can make some educated guesses about why this systematic overprovisioning of instances is occurring.
A few potential reasons include:
A need to provision instances with larger vCPUs in order to access instances with the required memory
A need to provision larger storage-optimized instances where the focus is is high data IOPS
Using some other ‘rule of thumb’ when provisioning such as the not-so-tried-and-tested ‘determine what I think I need then double it’ rule.
Clearly, there are a number of options which drive the performance and cost of cloud instances (VMs) including: the number of processor cores; the amount of RAM, storage capacity and storage performance, etc. Just focusing on one of these factors might not be overly useful, other than that we observe such extreme underutilization of one of these key components.
How much do cloud sizing choices matter?
Given the sheer volume of workloads moving to public cloud — some 80% of enterprises reported moving workloads to cloud in 2017 — it is critical to accurately determine, monitor and then optimize your compute resources is critical. If you think there’s a problem with improper cloud sizing in your environment, you may want to check out our recently published cloud waste checklist to identify other problem areas and take action to reduce costs.
There are many reasons why this “supersize me” approach to cloud sizing is occurring. We would be interested to get your take. How does your team determine compute requirements for cloud workloads? Are there other reasons why you might deliberately choose to oversize a resource? Comment below to let us know.