Your data warehouse is a different animal than most of your other cloud systems, due to:
The number of intersystem connections. From the front side and all the systems where you perform ETL, to the back side and all the different ways that the data is consumed, the number of system interconnects can easily cross into the hundreds, sometimes thousands. Even IoT systems with their large number of connections don’t handle much data per connection.
The shear amount of data. Not many operational systems deal in terabytes or petabytes of data. The simple act of copying data at this scale is never instantaneous and can take longer than you think. The typical response to this issue is to throw more (very expensive) bandwidth at the problem.
There are other reasons why it can be difficult to move from one cloud provider to another, but Teradata won’t be one of them.
When we talk to customers considering cloud implementation, they are often concerned about a minor, secondary effect: vendor lock in. While vendor lock in can be a problem, it’s usually not a major one. The major cloud vendors tend to have very similar capabilities when it comes to analytics. Often the applications used on one vendor can be installed and used on another with little or no change. With Teradata Everywhere, we support the two big cloud vendors, Microsoft Azure and Amazon Web Services. Teradata used on either platform (or on-premises or in VMWare) operate identically to each other. You can migrate your applications just by repointing the application, not recoding.
So, what are the real issues with migration? 
  1. Not having a good business reason and not knowing why you are migrating. This hiccup happens more often than most people think. We see it mostly when IT departments are chasing the “shiny new thing.” Without a clear vision of why you are changing providers, you don’t know when you are finished. Are you just trading headaches?
  1. Data egress charges that sneak up on you. We have seen customers moving 10-20 terabytes a day between cloud providers and then getting a shocking bill at the end of the month. Unlike operational systems that deal in small bursts of data, analytic platforms routinely churn through very large amounts of information.
  1. While cloud functionality is typically matched up, it’s normally accomplished in slightly different ways. Consider Azure Resource Groups versus AWS VPCs. Both are used for grouping but accomplish it in different ways that don’t directly translate. You can spend a lot of time and money trying to mimic one cloud functionality into another and don’t adopt the native model.
  1. Lastly, but by no means least, don’t underestimate educating the IT user community. While we like to talk about how it’s “transparent to the user,” large migrations rarely ever are. Have you discussed a cloud change with the business community and what it means to them?
There are other reasons why it can be difficult to move from one cloud provider to another, but Teradata won’t be one of them. IntelliCloud, as the core of an analytic ecosystem, can make this easier for you. We remove the non-productive (but required) work, such as system administration and maintenance so that we can handle it for you.
To learn more, follow the conversation at #CloudExperts or #BuiltForTheCloud, or reach out to your Teradata account team.
Ron Luebke
Ron supports international architecture and key needs for Teradata’s cloud initiative. With 25 years’ experience (including 15+ years using Teradata) in enterprise data management and strategy, Ron has diverse experience with Fortune 200 leaders in the agriculture, finance, telecommunications, health care, government and consumer goods sectors. He is involved in conceiving, creating and bringing to fruition innovations; combining thinking big with laboring through the pains of materializing ideas.
View all posts by Ron

Related Posts