BACKGROUND
Please describe your organization.
Midwest Cloud Computing provides private and public cloud solutions and managed service provider services, aimed at small and medium-sized businesses in the Midwest.
We work with Rackspace, Amazon Web Services [AWS] and Azure, in that order. We also have our own private solution that we market for cloud computing, with our own stack and datacenter.
What is your position?
I'm the managing partner within the company.
CHALLENGE
What is the typical business challenge that a client might be facing when they approach your company, inciting a need for a cloud platform?
Generally, they want to explore the possibility, but are lacking the resources that are internally required to help architect such a solution. They don't have a lot of familiarity with the differences between providers in the industry, and are looking for someone who can direct them.
SOLUTION
What would a typical implementation of a cloud platform look like for a client?
In an early-on engagement, we will discuss what the end-state looks like to them in terms of the problems they're trying to solve, whether if they are infrastructure-based, if they have complexities that they can no longer fix, and so on. There is a myriad of problems that can be brought to the table. Once we've created a robust problem statement, we'll look for the best provider of such services. If the client isn't specifically interested in the technology itself, and they simply want a service, we will probably opt for a Rackspace datacenter. They offer fanatical support.
We build a relationship with the hosting organization that the client will choose, and together with that organization, we create a migration plan, taking into consideration the percentage of virtualization the client currently has. They might be in a hybrid situation in which email and other services are in the cloud, but other elements are in-house. We bring these factors together, and once a project plan is in place, we will have an idea of what the requirements on their end and ours will be. If they sign the contract based on this, we engage; if not, we will catch up with them at 90 day intervals and assess their direction.
What are the specific reasons for which you would recommend either Rackspace, AWS, or Microsoft Azure to a particular client?
As a managed service and support provider, I've seen Rackspace's fanatical support in action. They have a very robust platform which does a good job of making the process simple and keeps the client's solution functional. Whenever an anomaly occurs, they keep you in the loop and explain what is happening.
Compared to legacy systems, what can an organization expect in terms of cost?
In my point of view, there are physical and logical costs. The physical costs involve platforms, capital expenditure and so on. They can be deferred by working with solution providers. Many companies get into the three to five year cycles of having to replace server hardware and other infrastructure elements, which can amount to millions of dollars. An in-house cost model also implies that 50% of the money is spent just to make sure that the lights are blinking.
From a logical cost perspective, the benefits and cost factors are centered around people. Applications have to be patched and updated. By moving to a hosted or cloud model, these costs see a sharp reduction.
An organization may have found the best database administrator on the planet. That person can still find another job at a different company. The cost of replacing talent isn't considered by many clients. Managed service providers come with that expertise.
Specifically when it comes to big data deployment, a MongoDB infrastructure will fetch a $150,000 price. A Midwestern company with a good MongoDB administrator will have that person snapped up from them by the West or East Coast.
A hosting environment has the responsibility of bringing that expertise to the table. This is a huge advantage. When such a key person is lost, your project will be sunk. After a company has invested millions of dollars in Hadoop and in business analytics time, if their star administrator is lost to another company, they're done.
FEATURES
Are there any particular features of tools on any of these platforms that might make them stand out compared to others?
I've worked with Rackspace on a product that we call “big data in a box”. We're able to provide the entire infrastructure, like Hadoop, NoSQL and MongoDB in one place. The client can jump ahead to step 25 on the project plan, so they can actually focus on business analytics. From an advantage perspective, Rackspace enables users to host their existing workloads from Azure, AWS or other legacy platforms. They're agnostic from a functionality perspective, whereas Azure and AWS don’t cross-pollinate.
Are there any key areas that these platforms could improve?
I can't say anything negative about Rackspace. They're large and employ lots of people. The only thing I would mention is that it's a compartmentalized service. If you have a specific need and don't find the right person to help, you will waste a lot of time finding a solution.
OVERVIEW
We have five additional questions. For each of these, we ask that you rate each service on a scale of one to five, with five being the best score.
How would you rate each platform for its functionality and available features?
Four and a half.
How would you rate them for ease of use and implementation?
Four.
How would you rate them for their support services in terms of their teams' responsiveness and helpfulness of available resources?
Five.
How likely are you to recommend each platform to a friend or colleague, out of five?
Five.
How would you rate your overall satisfaction with each platform?
Four and a half.
