Monday, June 20, 2011

Software Dependencies – the Big Hitch in Cloud Computing

I will start this article with a joke by Dave Platt (software legend)

How did God manage to create the earth in just 6 days?
-          He did not have any legacy applications
I find this joke quite relevant when it comes to moving applications to the cloud. Either it`s a private cloud, or a public cloud.

It is quite obvious that the biggest problem that every organization face when they consider moving some or all of their applications systems to the cloud, are the software dependencies.
Remember that the cloud uses a SOA approach where these services are loosely coupled together.
In VMM 2012, you`ll see how Microsoft has brought this into the private cloud with the possibility to create services, which is a combination of various tiers of applications, servers, and virtual machines.
But again, it is important that the application itself can be loosely linked.
All of the applications (in theory) running in the datacenter, share infrastructure and data. However, as companies begin migrating applications (or data or storage) into the cloud; these applications need to be designed to support technical independence.

As part of the planning process, you need to do a full inventory of applications and systems that must or at least should – be moved together.
The interdependencies determine this, whatever their perspective:

1)      Hardware perspective (are there any need for a specific CPU etc.)
2)      Platform perspective (do your applications require a specific operating system, and a given middleware product)
3)      Software perspective (are there any services that need to be closely coupled with related applications)

Less dependencies = more flexibility
Establishing this architectural approach, in effect, creates containers of functionality within the datacenter that ease the transition to the cloud.

No comments: