Is your Cloud provider outcome-based or merely technology-focused?
Most companies that are looking to transition to a Cloud-based model often get hung up on the technology side of the equation. Assessing projected capacities, load balancing, and memory throughput rates are all well and good – these things are all part of the due diligence process, after all.
“You can check out any time you like, but you can never leave” – that’s true not only for the well-known hotel in The Eagles’ song, but also in many lines of business when talking about paradigm shifts and pervasive changes we’ve faced over the past several years. Nowadays, cars are more and more being leased, borrowed and shared, newspapers and TV are consumed online, servers and memory are accessed only when required.
Migrating a traditional application to the cloud isn't as complex as it sometimes first appears. We frequently work with our clients to make this transition, and have compiled three of the most common misconceptions about moving from a dedicated server deployment to a cloud environment.
One of our favorite themes about what people love about the cloud is the idea of “Frictionless Sales”. That’s the ability for our clients to to scale up and down seamlessly on their usage hourly and only pay for what they use. Our largest cloud client uses that Frictionless Model exclusively and is currently adding 400 servers a week sending API commands. That has equated to millions of dollars a year in cloud revenue at 6.5 cents an hour.
While all public cloud service providers seem to offer a similar level of service, there are fundamental differences between cloud providers that significantly impact performance, cost and usability. This in turn influences what applications and workloads will run well on a cloud provider’s platform.
I can't express how excited I am about Dimension Data Cloud's new Tiered Storage offering. While we have consistently added new features over the last three years, this is the one I've most anticipated. It finally addresses the Achilles heel of cloud environments − the struggle to run traditional relational databases in a constrained disk I/O environment.
One of the most popular sales inquiries our team fields is related to the desire to build a DR site for a SaaS or IT application. However, despite the popularity of this question, very few clients follow through with implementing a true disaster recovery solution due to the costs complexities involved.
Over the last few years, we've been through hundreds of these discussions with clients, and we've seen our clients waste a lot of time developing solutions that are never implemented. Through these conversations, we have learned a lot about which situations are likely to result in a DR implementation and which will condemn a client to live perpetually in the "we should implement DR" phase.