When Too Much Control Is a Bad Thing

James Staten

I know, more control is an axiom! But the above statement is more often true. When we're talking about configuration control in the public cloud it can be especially true, as control over the configuration of your application can put control in the hands of someone who knows less about the given platform and thus is more likely to get the configuration wrong. Have I fired you up yet? Then you're going to love (or loathe) my latest report, published today. 

Let's look at the facts. Your base configuration of an application deployed to the cloud is likely a single VM in a single availability zone without load balancing, redundancy, DR, or a performance guarantee. That's why you demand configuration control so you can address these shortcomings. But how well do you know the cloud platform you are using? Is it better to use their autoscaling service (if they have one) or to bring your own virtual load balancers? How many instances of your VM, in which zones, is best for availability? Would it be better to configure your own database cluster or use their database as a service solution? One answer probably isn't correct — mirroring the configuration of the application as deployed in your corporate virtualization environment. Starting to see my point?

Fact is, more configuration control may just be a bad thing.

Read more

Forrester Wave: Public Cloud Platforms -- The Winner Is…

James Staten

…not that simple and therefore not always Amazon Web Services.

First off, we didn’t take what might be construed as the typical approach, which would be to look either at infrastructure-as-a-service (IaaS) or platform-as-a-service (PaaS) offerings. We combined the two, as the line between these categories is blurring. And historical category leaders have added either infrastructure or platform services that place them where they now straddle these lines.

Further, many people have assumed that all developers will be best served by PaaS products and ill served by IaaS products. Our research has shown for some time that that isn't so: 

  1. Many developers get value from IaaS because it is so flexible, while PaaS products are generally too constraining.
  2. The -aaS labels overlook the actual capabilities of the services available to developers. All PaaS products are not the same; all IaaS are not the same.
  3. Not all developers are the same. Devs will use the services (PLURAL) with the best fit to their skills, needs, and goals.
Read more