Welcome!

Microservices Expo Authors: David Green, Elizabeth White, Ruxit Blog, Liz McMillan, Sematext Blog

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, Agile Computing, @BigDataExpo, SDN Journal

@CloudExpo: Article

Top Three Best Practices for Migrating to the Cloud

Planning your migration strategy

As an Infrastructure-as-a-Service provider, Bluelock sees a lot of migration of applications. Migration is occurring from physical servers to cloud, from private cloud to public cloud and back to private cloud from public cloud.

Migration can be tricky and a poor migration strategy can be responsible for costly time delays, data loss and other roadblocks on your way to successfully modernizing your infrastructure.

While each scenario is different, I'd like to identify three key best practices that will help your team create a solid, successful plan for migrating your application.

Even before you begin to move your application, there's a lot of best practice that goes into choosing which application to migrate to the cloud. Regardless of whether you are migrating that app to a public cloud or a private cloud, you should assess the app for data gravity and connectivity of the application.

Best Practice: Understand the Gravity of Your Data
Data Gravity is a concept first discussed by Dave McCrory in 2010. It's the idea that data has weight and the bigger the data is, the harder it is to move. The bigger the data, the more things are going to stick to it.

McCrory states in his original blog post about Data Gravity, "As data accumulates (builds mass) there is a greater likelihood that additional Services and Applications will be attracted to this data."

McCrory goes on to explain that large data can be virtually impossible to move because of latency and throughput issues that develop upon movement. On his website, datagravity.org, McCrory explains that to increase the portability of an application it should have a lower data gravity.

When moving tier one applications from a physical datacenter to a private or public cloud, we have to take data gravity into account because it will impact the migration.

As you are talking about migrating an application, you can think of the full stack of components as a single VM or a group of VMs that are a vApp (see Figure 1).

Think of a VM with an OS. If we were to migrate that entire VM to the public cloud, we're copying anywhere from 8-20 GB of data with that OS for no reason at all as the cloud you're migrating the app to might already have the OS available to it.

Rather than transferring the data for the OS, whenever possible use metadata instead to describe what OS you want and the configurations using a template or an image on the public or private cloud side. The same metadata concept can be applied to middleware instances too.

What we're left with is our actual data and what the app is. The app is static and static info is easy to move because you can copy it once. There's no need to replicate.

The most difficult part of the migration is the data, however. There's no easy way to shrink down the data, so you need to evaluate the weight of the data in the app you're considering migrating.

Especially if you're a high transaction company, or if it's a high transaction application, as that would be a lot of data to replicate. The data of the app constitutes 99% of the data gravity of the application.

Part of the best practice of understanding the gravity of your application is to understand the ramifications of moving a tier one application with a large amount of data and establish where the best home for that application is.

Another aspect that you should evaluate as part of your pre-migration plan is to determine how connected your VM or vApp is to other apps.

If you have a lot of applications tightly coupled to the application you want to migrate, the cloud might not be an option for that application, or at least only that application.

Best Practice: How Connected Is Your App?
Beyond what applications are connected to the app you want to migrate, the important aspect to evaluate is how coupled the application in question is to other applications, and how tight or loose of a couple they are.

Does your application have data that other applications need to access quickly? If so, a move all or nothing philosophy is your best option.

If you have an application that is tightly coupled to two or three others, you may be able to move them all to the cloud together. Because they are still tightly coupled, you won't experience the latency that would occur if your cloud-hosted application needed to access a physical server to get the data it needs to run.

A step beyond identifying how many apps are tied to the application you wish to migrate, work next to identifying which of those applications will be sensitive to latency problems.

How sensitive it can be should be a consideration of whether you should migrate the app or not.

To be able to check this best practice off your list, be very sure you understand everything your application touches so you won't be surprised later, post-migration.

The final part gets down to the nitty gritty... choosing the correct migration strategy.

Best Practice: Pick Your Migration Strategy.
Your best-fit migration strategy will be a function of the features of the application.

Option one is data migration of just the data. This is typically the correct choice for tier 1 and 2 applications.

Let's say you are able to migrate your VM or vApp. But, it's constantly changing and if it's a tier one application, we may not be able to afford a lot of downtime. Typically, we'll have to invoke some sort of replication.

Replication is an entirely separate subject, but when I think of replication, I think of the size of the data, the rate of change and the bandwidth between our source and target.

Without going into too many details of replication, let's assume you use some sort of SQL or MySQL program for database replication. What you've done is set up your new cloud to have this OS provision. You've got a MySQL provision and the two SQLs are talking to each other and replicating the data.

Option two for migrating your application is machine replication. This is best for tier 1 and tier 2 applications that can afford some downtime. It involves stack migration. There is less configuring in this scenario, but there is more data migrating.

Option two is best if you're moving to an internal private cloud. You will be able to replicate the entire stack because you have plenty of bandwidth to move stuff around.

It's important to note the portability of VMware, because VMware allows you to package the entire VM/vApp, the entire stack, into an OVF. The OVF can then be transported anywhere if you're already on a virtualized physical server.

Option three involves cold P2V migration. You typically see this for tier 2 and 3 apps that are not already virtualized.

The concept involves taking a physical app and virtualizing it. VMware has a VMware converter that does P2V, and it's very easy to go from a physical to a private cloud using P2V. It is, however, an entirely different set of best practices.

In option three, there is no replication. Those apps can also be shipped off to a public cloud provider to run in the public cloud after being virtualized.

A final path some companies take is to treat it as a Disaster Recovery (DR) scenario. Setting up something to basically do replication from one machine to another. Replicate the entire stack from point a to point b, and then click the failover button.

Each application, and migration strategy, is unique, so there is no detailed instruction manual that would work for everyone. The best strategy for some applications may be to stay put, especially if you find that steps one and two of the pre-migration evaluation is closely connected or especially weighty. To truly enjoy the benefits of cloud, you want the right application running that you can leverage to the fullest extent.

When planning your migration strategy, ask for help from those who are familiar with similar use cases and plan and evaluate extensively to save yourself a lot of time, money and headaches that come from rushing into a migration without a strategy.

More Stories By Jake Robinson

Jake Robinson is a Solutions Architect at Bluelock. He is a VCP and former CISSP and a VMware vExpert. Jake’s specialties are in infrastructure automation, virtualization, cloud computing, and security

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
SYS-CON Events announced today that eCube Systems, a leading provider of middleware modernization, integration, and management solutions, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. eCube Systems offers a family of middleware evolution products and services that maximize return on technology investment by leveraging existing technical equity to meet evolving business needs. ...
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
This complete kit provides a proven process and customizable documents that will help you evaluate rapid application delivery platforms and select the ideal partner for building mobile and web apps for your organization.
Monitoring of Docker environments is challenging. Why? Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and applications they run. These servers and applications running on them are typically very static, with very long uptimes. Docker deployments are different: a set of containers may run many applications, all sharing the resource...
With so much going on in this space you could be forgiven for thinking you were always working with yesterday’s technologies. So much change, so quickly. What do you do if you have to build a solution from the ground up that is expected to live in the field for at least 5-10 years? This is the challenge we faced when we looked to refresh our existing 10-year-old custom hardware stack to measure the fullness of trash cans and compactors.
The emerging Internet of Everything creates tremendous new opportunities for customer engagement and business model innovation. However, enterprises must overcome a number of critical challenges to bring these new solutions to market. In his session at @ThingsExpo, Michael Martin, CTO/CIO at nfrastructure, outlined these key challenges and recommended approaches for overcoming them to achieve speed and agility in the design, development and implementation of Internet of Everything solutions wi...
Node.js and io.js are increasingly being used to run JavaScript on the server side for many types of applications, such as websites, real-time messaging and controllers for small devices with limited resources. For DevOps it is crucial to monitor the whole application stack and Node.js is rapidly becoming an important part of the stack in many organizations. Sematext has historically had a strong support for monitoring big data applications such as Elastic (aka Elasticsearch), Cassandra, Solr, S...
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
SYS-CON Events announced today that 910Telecom will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Housed in the classic Denver Gas & Electric Building, 910 15th St., 910Telecom is a carrier-neutral telecom hotel located in the heart of Denver. Adjacent to CenturyLink, AT&T, and Denver Main, 910Telecom offers connectivity to all major carriers, Internet service providers, Internet backbones and ...
Before becoming a developer, I was in the high school band. I played several brass instruments - including French horn and cornet - as well as keyboards in the jazz stage band. A musician and a nerd, what can I say? I even dabbled in writing music for the band. Okay, mostly I wrote arrangements of pop music, so the band could keep the crowd entertained during Friday night football games. What struck me then was that, to write parts for all the instruments - brass, woodwind, percussion, even k...
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...

Modern organizations face great challenges as they embrace innovation and integrate new tools and services. They begin to mature and move away from the complacency of maintaining traditional technologies and systems that only solve individual, siloed problems and work “well enough.” In order to build...

The post Gearing up for Digital Transformation appeared first on Aug. 30, 2016 05:45 PM EDT  Reads: 1,722

DevOps at Cloud Expo – being held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Am...
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 19th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The Internet of Things (IoT) is the most profound change in personal and enterprise IT since the creation of the Worldwide Web more than 20 years ago. All major researchers estimate there will be tens of billions devices - comp...
Thomas Bitman of Gartner wrote a blog post last year about why OpenStack projects fail. In that article, he outlined three particular metrics which together cause 60% of OpenStack projects to fall short of expectations: Wrong people (31% of failures): a successful cloud needs commitment both from the operations team as well as from "anchor" tenants. Wrong processes (19% of failures): a successful cloud automates across silos in the software development lifecycle, not just within silos.
19th Cloud Expo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Meanwhile, 94% of enterpri...

Let's just nip the conflation of these terms in the bud, shall we?

"MIcro" is big these days. Both microservices and microsegmentation are having and will continue to have an impact on data center architecture, but not necessarily for the same reasons. There's a growing trend in which folks - particularly those with a network background - conflate the two and use them to mean the same thing.

They are not.

One is about the application. The other, the network. T...

As the world moves toward more DevOps and Microservices, application deployment to the cloud ought to become a lot simpler. The Microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. Serverless computing is revolutionizing computing. In his session at 19th Cloud Expo, Raghav...
The following fictional case study is a composite of actual horror stories I’ve heard over the years. Unfortunately, this scenario often occurs when in-house integration teams take on the complexities of DevOps and ALM integration with an enterprise service bus (ESB) or custom integration. It is written from the perspective of an enterprise architect tasked with leading an organization’s effort to adopt Agile to become more competitive. The company has turned to Scaled Agile Framework (SAFe) as ...
If you are within a stones throw of the DevOps marketplace you have undoubtably noticed the growing trend in Microservices. Whether you have been staying up to date with the latest articles and blogs or you just read the definition for the first time, these 5 Microservices Resources You Need In Your Life will guide you through the ins and outs of Microservices in today’s world.