Replicating the efficiency and engineering of a shark in the data center is certainly something to strive for, but challenging. Trying to think of how the shark metaphor would apply to a cloud implementation.
BTW, we did our #CIOchat Twitter chat on this topic last week. As usual, there was no consensus, which I attribute to a healthy and candid discussion. Use the hastag #CIOchat between 2-3 p.m. EDT last Thursday (6/25). We'll be back at the same time this Thursday.
I promised you a part II to my 2015 predictions and here they are. In part I, I focused largely on the cloud and many of its moving parts. I am a little more expansive here. As always, let me know what you think.
How can you match up the promise of the cloud with the twin goals of reducing costs and enhancing customer responsiveness? From afar, it seems easy, but reality can be entiurely another matter. Here are a few pointers to help you accomplish your goals as you transition to the environment of the future.
Start by developing your future target environment
It’s all about “Platform as a Service” these days. But juxtaposed to Infrastructure as a Service (IaaS), what does PaaS mean, and how do you make the right choice for a given application? I see at least two different kind of PaaS environments addressing different scenarios and needs. It’s important, when embarking on the development and/or migration of an application to a cloud environment, to thoroughly think through which PaaS environment to use.
Infrastructure teams tend to think shorter term and as a consequence are often ill-suited to lead cloud migrations. How do I know? I've had contact with three customers recently where the marching orders were to move quickly and invest as little as possible in the migration. The goal was to reduce costs move by shuttering data centers and manage multiple suppliers.