Distributed cloud service is a growing phenomenon. It fills several roles, distributing data for use by distributed applications, for data protection, and for other reasons. We have been seeing an increase in the number of distributed applications. Non-distributed applications lack the resiliency that is required to work within a cloud, whereas distributed workloads add a certain amount of resiliency to an application. Depending on how they are architected, the lack or failure of one part of a distributed application won’t bring down the entire application. Use of multiple clouds ensures your eggs are not all in one basket, so to speak.
Articles Tagged with cloud migration
In my post A Look Forward to 2015, I mentioned the drastic jump in revenue that Microsoft has had with the growth of its cloud services, including Microsoft Azure, Office 365, and Microsoft Dynamics, as well as other SaaS platforms. When you look at the array of products and services Microsoft has developed, it’s clear that Microsoft is gearing up to take the title from the current reigning cloud champion, Amazon. When will Microsoft overtake its rival? Time will tell, but my safe bet is that it will be within the next five years.
Are things becoming too automated? That is a question I cannot believe I am asking. I have spent most of my virtual career creating automated processes from my virtual environments. I spent a great deal of time creating a “toolbox” of scripts to perform almost all of the tasks that I found myself needing to do in an automated fashion. A lot of my peers and I were all creating automated build and automated configuration of our environments from the very beginning and now are seeing a great deal of the automation that we created in one way or another being added to the product suite. Is that a bad thing? No, on the contrary, this shows the active deployment of the technology and gives us insight to the direction the technology may follow.
On December 18, I had an interesting Twitter conversation with Mark Thiele (@mthiele10) about moving to the cloud based on cost. There is a cost perspective to consider as cloud services can be very expensive. When does it make sense to go to the cloud? There are two scenarios to consider when talking about going to the cloud. While we were hampered by the 140-character limit, I think the message is clear.
Mike DiPetrillo’s post entitled VMware is Building Clouds sparked some interesting thoughts and discussion about what it means to have federated clouds and how do you define such federation? Is federated required to make ‘cloud’ ubiquitous or are we already there? But is the discussion really about federated clouds or simplistic data object movement between the VMs or about cloud management?
When we talk about cloud data we often speak about moving virtual machines around, but is that the proper way to do this? Given that a VM could be 100s of gigabytes, could the movement between clouds happen fast? What about the runtime and security contexts that surround the data to be moved (whether a VM or not). Does this move with the data object or does it stay within the source environment. I have this question regardless of cloud type.