This one, I coined in the context of the currently occurring, overwhelmingly prevalent cloud migration efforts in IT. In my own experience, the favored approach, given a business' urge to adopt the buzz word and be able to say that they are "in the cloud," is "lift and shift."
What a vast majority seem to believe is that they can pick up their current applications and infrastructure and move it "the cloud," and immediately get the benefits that are available with cloud functionality.
What is not understood is something is a little fact that I have on a sticker on my laptop: "There is no cloud. It is just someone else's computer." To truly leverage the benefits of a cloud approach requires study, design, architecture, and refactoring. The companies with professionals who understand that make a plan to migrate to the cloud. They understand the capabilities available and strategically determine which pieces of functionality make the most sense for this refactoring effort.
The ones who do not, have a migration plan that I term "lift and sh*t." The existing applications and infrastructure are moved to "someone else's servers," and similarly do not have the appropriate logging, monitoring, or standards in development that would actually make even a remote infrastructure make sense. So yes, they are in the cloud, and have "lifted." They've accomplished absolutely nothing in the doing though, can leverage none of the value, and have less visibility into any issues that may arise and ultimately end up with a degraded product and application --and very unhappy customers.
Comments