By Jung Hwang, Enterprise Solutions Architect, VMware
Imagine you are a general contractor building a house for a family. Without meeting them, you decide it should have three bedrooms, two bathrooms, and a two-car garage. When the family moves in, you have to begin renovating immediately—they have four teenage daughters and a baby on the way.
We all know that adding another bedroom, another bathroom, and doubling the garage is more costly and time consuming than it would have been to build the house to fit the family in the first place. So why do IT organizations so often make the same mistake when building out the Infrastructure as a Service (IaaS) environment?
I recently saw this with a large financial institution that deployed their infrastructure to support an initial set of low complexity infrastructure use cases. Everything went fine until they started adding other IaaS use cases, including Database as a Service (DBaaS) and Big Data as a Service (BDaaS). To accommodate larger, faster, low latency, and high IO workloads, they were forced to scale up their existing blade servers but discovered their NFS storage environment wasn’t sufficient to support the new workloads. They ended up redesigning their underlying hardware platform, including compute, storage, network, and security.
It seems obvious that a lot of “renovation” could be saved by understanding which services will “live in the house” first. So why do IT organizations often fail to employ that foresight? Continue reading