Yesterday (Sept. 24), I attended a cloud summit seminar sponsored by the Object Management Group’s Cloud Standards Customer Council. This was not about scrutinizing lines of code, but rather, an examination of real-world situations as seen through the eyes of cloud consultants, architects, and select major vendors.
What I learned could have come from the mind of Forrest Gump, who famously said, “Stupid is as stupid does.”
David Linthicum, senior vice president at Cloud Technology Partners and a TechTarget contributor, was the first to say it: “If you take a crappy application that exists on a platform internally and put it in the cloud, it’s just a crappy application in the cloud.”
In her presentation, Pamela Wise-Martinez, senior enterprise architect at the Pension Benefit Guaranty Corporation, hammered home the same point. “You’ve got to see how cloud-ready your applications are. If it’s a crappy application and you put it in the cloud, it’s still crappy. You’ve got to make intelligent decisions about what goes to the cloud.”
In other words, crappy is as crappy does.
Sure, we all want to move everything, or nearly everything, into the cloud. These speakers, though, are making a couple of important points. First, some applications, not matter how well built, simply don’t belong in the cloud. That might be factory floor process control or retail back-room administrative functions. Second, applications that would benefit from being in the cloud might be built in a way that makes them cloud unfriendly. If you want the functionality of those apps in the cloud, the existing code base may need to be thrown out and replaced with something else.
What’s your plan for moving on-premises, legacy applications into the cloud? Have you figured out which apps are good candidates and which are not? Or did you learn the hard way, only after attempting a migration? Share your thoughts, we’d like to hear from you.