Why Large-Scale Enterprises Are Migrating to the Cloud
Regardless of the industry, just about every company has become a technology company out of necessity. Your enterprise breathes through IT, and if you’re limited to on-premises servers then you’re likely giving your competitors an advantage. Migrating to the cloud means breaking away from the technologies that are holding you and your enterprise back from the speed, scalability, and cost savings that the cloud has to offer.
Cloud migration is about moving your data, applications, and even infrastructure from your on-premises computers or infrastructure to a virtual pool of on-demand, shared resources that offer compute, storage, and network services at scale.
Rather than continuing to invest in aging and expensive infrastructure that can’t keep pace with the changes in modern technology, migrating to the cloud is a choice for the future. In addition to the immediate benefits of cost savings and scalability that can be realized, you are essentially laying the foundation to be able to respond more quickly to changes in the market, scale your growth, and drive innovation for the long term.
As you’re planning your cloud migration, understanding how to get there depends on your unique business model and goals as well as your current infrastructure and applications. You’ll need to rely on the skills and experience of your IT teams to understand the ins and outs of your current environment and the interdependencies of your applications to determine which applications to migrate and how. The “5 Rs of cloud migration” from Gartner are a great place to start when considering all of the options for migrating your applications to the cloud.
Whether it’s your initial migration or your fifth iteration, your cloud migration requires a strategy and planning to be successful. Here’s what you need to know.
The 5 “Rs” of Cloud Migration: Rehost, Refactor, Revise, Rebuild, and Replace
Rehosting is the process of moving your existing physical and virtual servers to a solution based on Infrastructure as a Service (IaaS). Also known as lift and shift, the key benefit of this approach is that systems can be migrated quickly with no modification to their architecture. This is often the path that companies take when they’re new to cloud computing. When rehosting, you’re basically treating the cloud as just another data center, which means you’re not getting the most out of the available cloud services.
Consider a web application as a simple example. Imagine you have an ASP.NET application running on Windows and you want to rehost it on AWS. You can create a Windows VM that meets the size requirements and deploy the application. With a change to the DNS record, you’re pretty much ready to go live. In this way, rehosting is an easy way to move to the cloud. However, this solution isn’t highly available, or scalable, and it still requires you to manage OS patches.
This is the process of running your applications on the infrastructure of your cloud provider, also referred to as Platform as a Service (PaaS). PaaS means that developers are able to reuse the frameworks, languages, and containers in which they’ve already invested. For applications or workloads that can be refactored to leverage cloud capabilities, you’ll be able to take advantage of some cloud-native features offered by the PaaS infrastructure for reduced costs and increased scalability. However, the biggest disadvantages of this option include transitive risk, missing capabilities, and framework lock-in. One of the common issues that developers run into here is that many PaaS options use ephemeral storage. This typically requires a change to the codebase to use cloud storage, rather than the local file system for saved files.
An example of refactoring to use PaaS might be to take an existing Ruby on Rails application and deploy it to Heroku or to take an existing Drupal application and modify it to run on Acquia Cloud or Pantheon. PaaS options will allow you to focus on the application without having to deal with the underlying OS.
Certain applications will need to be modified more extensively in order to migrate them to the cloud. Some will require added functionality while others may need to be re-architected completely before they can be rehosted or refactored and eventually deployed to the cloud.
This can be a difficult option because modifying a large codebase to become more cloud-native can be time consuming and expensive. An example would be taking a complex, monolithic Python-based application and moving it to Google App Engine. The design of your application will determine the amount of changes you’ll require. You may find that you need to break it out into multiple applications and swap out components such as message queues to get the most out of the move.
In this scenario, an application is re-architected, original coding is discarded, and it is re-built on a PaaS infrastructure. Rebuilding the application allows you to take advantage of more advanced and innovative features from your cloud provider to improve your application even further. A major drawback of this option is vendor lock-in.
For instance, if the provider makes a technical or pricing change that the customer cannot accept or that breaches the service level agreement (SLA), the customer may be forced to switch back to the previous application, potentially losing some or all of its application assets.
For example, you may rebuild your application so that it is completely serverless. By using technologies such as AWS Lambda, API Gateway, DynamoDB, S3, and others, you could run your application without having to manage servers for yourself. This sort of cloud-native application would be inexpensive to operate and highly scalable. However, it also means that you’re locked in to using a particular cloud vendor. This isn’t intrinsically bad, but it is a factor that you will need to consider.
In this scenario, you completely replace the existing application(s) with software delivered as a service (SaaS). An advantage of the replace model is that it allows you to avoid IT development costs. However, you may encounter problems in accessing data, unpredictable data semantics, and vendor lock-in.
This can be a great option for minimizing the amount of services and applications that you need to manage. An example might be to replace your local database with a managed option such as Cloud Datastore, Cosmos DB, or Dynamo. This can be one of the easiest ways to bring up your SLA. These services are all known for their scalability and availability. In contrast, running a database yourself and dealing with data replication and failover can be a lot of work.
The Bottom Line: Migration Projects of Any Size Require Careful Planning
A successful cloud migration requires careful preparation and planning. There is no one-size-fits-all approach to migrating to the cloud. Your teams will need a deep knowledge of the infrastructure and applications that your business runs on in order to fully understand the complexity, challenges, and costs involved.
Some great content to get you started on Cloud Migration:
Advantages and Disadvantages of Microservices Architecture
What are microservices? Let's start our discussion by setting a foundation of what microservices are. Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs). ...
Kubernetes Services: AWS vs. Azure vs. Google Cloud
Kubernetes is a popular open-source container orchestration platform that allows us to deploy and manage multi-container applications at scale. Businesses are rapidly adopting this revolutionary technology to modernize their applications. Cloud service providers — such as Amazon Web Ser...
AWS Internet of Things (IoT): The 3 Services You Need to Know
The Internet of Things (IoT) embeds technology into any physical thing to enable never-before-seen levels of connectivity. IoT is revolutionizing industries and creating many new market opportunities. Cloud services play an important role in enabling deployment of IoT solutions that min...
Which Certifications Should I Get?
As we mentioned in an earlier post, the old AWS slogan, “Cloud is the new normal” is indeed a reality today. Really, cloud has been the new normal for a while now and getting credentials has become an increasingly effective way to quickly showcase your abilities to recruiters and compan...
How to Go Serverless Like a Pro
So, no servers? Yeah, I checked and there are definitely no servers. Well...the cloud service providers do need servers to host and run the code, but we don’t have to worry about it. Which operating system to use, how and when to run the instances, the scalability, and all the arch...
AWS Security: Bastion Hosts, NAT instances and VPC Peering
Effective security requires close control over your data and resources. Bastion hosts, NAT instances, and VPC peering can help you secure your AWS infrastructure. Welcome to part four of my AWS Security overview. In part three, we looked at network security at the subnet level. This ti...
Top 13 Amazon Virtual Private Cloud (VPC) Best Practices
Amazon Virtual Private Cloud (VPC) brings a host of advantages to the table, including static private IP addresses, Elastic Network Interfaces, secure bastion host setup, DHCP options, Advanced Network Access Control, predictable internal IP ranges, VPN connectivity, movement of interna...
Big Changes to the AWS Certification Exams
With AWS re:Invent 2019 just around the corner, we can expect some early announcements to trickle through with upcoming features and services. However, AWS has just announced some big changes to their certification exams. So what’s changing and what’s new? There is a brand NEW ...
New on Cloud Academy: ITIL® 4, Microsoft 365 Tenant, Jenkins, TOGAF® 9.1, and more
At Cloud Academy, we're always striving to make improvements to our training platform. Based on your feedback, we released some new features to help make it easier for you to continue studying. These new features allow you to: Remove content from “Continue Studying” section Disc...
AWS Security Groups: Instance Level Security
Instance security requires that you fully understand AWS security groups, along with patching responsibility, key pairs, and various tenancy options. As a precursor to this post, you should have a thorough understanding of the AWS Shared Responsibility Model before moving onto discussi...
Cloud Migration Risks & Benefits
If you’re like most businesses, you already have at least one workload running in the cloud. However, that doesn’t mean that cloud migration is right for everyone. While cloud environments are generally scalable, reliable, and highly available, those won’t be the only considerations dri...
Real-Time Application Monitoring with Amazon Kinesis
Amazon Kinesis is a real-time data streaming service that makes it easy to collect, process, and analyze data so you can get quick insights and react as fast as possible to new information. With Amazon Kinesis you can ingest real-time data such as application logs, website clickstre...