Cloud data co-location prototype
The cloud data co-location use case is a very interesting one. Potentially the biggest reasons why organizations choose not to move a workload to the cloud include: compliance / regulatory requirements lock-in risks and difficulty/costs of migrating to another public/private cloud unpredictable and/or high costs These reasons also play an important part in the ongoing workload repatriation activity we are seeing in the market. The idea that "cloud is not a destination, it's an operating model" is finally sinking in. But, when we talk about destinations, it doesn't all have to be public or private. There is a third location that plays an interesting part Last year I participated in a project that studied the feasibility of implementing "cloud data co-location". This basically consists on hosting a traditional storage array in a datacenter that is physically close to a public cloud and connect to it through a high-throughput low-latency link. Some