Skip Links

What not to put in the cloud

A guide to which apps are right for cloud, and which apps aren't

By Jake Robinson, solutions architect, Bluelock, special to Network World
November 26, 2012 02:56 PM ET

Page 2 of 2

What doesn't work

From patterns we've seen, there are a few types of applications you should beware of moving to the public cloud. They might not achieve a greater ROI in public cloud than they could in private cloud or another internal environment. However, applications are dynamic and there are always exceptions to the rule.

RULE: Mature, stable mission-critical apps should not live in public cloud. As mentioned in the life cycle description, value from cloud typically doesn't come from the stable, predictable time frame of its life. Bursty and growing or declining applications get more value and a higher ROI in the public cloud than stable applications do, which is why it's recommended to host stable apps in your private cloud.

EXCEPTION: SaaS mission-critical applications often thrive in public cloud. A mission-critical software-as-a-service (SaaS) application often lives its entire life cycle in the public cloud. The main reason SaaS applications stay in the cloud forever is because in most cases they are green-fielded in the cloud and constantly rely on the elasticity of IaaS to continually grow and contract the environment as usage patterns swing. SaaS apps usually follow a similar pay-as-you-go billing pattern and it's most cost-effective to match infrastructure costs with revenue.

RULE: Highly integrated, business-critical apps should stay where they are. Any highly integrated business app, like your ERP or your finance applications, should stay where they are because it would be nearly impossible to move the application without causing problems that would grind business processes to a halt. Your ERP is your logistics system and you can't get more integrated than that. Any application that would halt operations if you moved it wouldn't be worth moving.

EXCEPTION: Only rarely will you have an exception to this rule. One exception might be that you don't have an ERP solution yet and you're looking to start one. As long as you aren't already integrated into the business, it can make sense to start off in the cloud so you have the benefits from the start and don't have to worry about the mobility of it later. It's possible that if you're young and looking for integrated solutions, than going to a SaaS solution will make sense. The key question is, "Have you already done the integration?" If not, then you can do a cloud-based SaaS because it's probably better in the long run.

RULE: Bursting into the public cloud doesn't work. There's a general understanding that you can have your application live in your internal environment and when it needs more room you can "burst" those extra resources into the public cloud. It's an idea of bursting between clouds and owning the base while renting the burst. That idea isn't widely in use because it hasn't been successful yet. The required technologies are not as agile as they need to be to create the desired efficiencies.

EXCEPTION: There are two types of cloudbursting that are in wide use and capitalize on the benefits public cloud has to offer: horizontal burst and vertical burst. Vertical cloudbursting refers to intracloud application burst when your application lives in a cloud with enough room and resources to burst up to a certain percentage. This is intracloud burst because it's bursting into the same cloud in which it's living. [Also see: "Gartner: Cloud computing's most over-hyped terms"]

Horizontal burst, or intercloud burst, is how bursting between clouds is working most commonly right now, but it isn't following the "burst-into" philosophy commonly thought of. Rather, it refers to moving other smaller applications off to the public cloud purely so you have the room and resources to allow your private cloud applications to burst within their private cloud without reaching capacity. There may be no more benefits from moving those smaller, stable workloads off to public cloud other than allowing room for your private cloud applications to be able to burst.

Based on the characteristics and life cycle of enterprise applications running in the cloud, you should start to have a good idea what will and won't work. You shouldn't try to shoehorn cloud into your strategy by dumping every app you have into public cloud immediately; it might not get you the most efficient, economic results possible.

Don't just rush to pick the applications that are consuming the most pain, or consuming the most resources, or the most data. Chances are those are your mission-critical apps which could be highly integrated to other apps that would also need to move to the cloud. Cloud is not a cure-all prescription for your IT pain points; rather it works harder for you when you're strategic about which applications are placed in which environments. Success is about executing a total cloud strategy for each application.

Read more about cloud computing in Network World's Cloud Computing section.

Our Commenting Policies
Cloud computing disrupts the vendor landscape


Latest News
rssRss Feed
View more Latest News