- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
Network World - This vendor-written opinion has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter's approach.
The powerful storms that recently hit the mid-Atlantic region caused electrical outages that in turn disrupted Amazon's EC2 services. The impact to the consumers and businesses that depend on the Amazon cloud have been well chronicled.
Amazon is a leader in reliability and, if it happens to them, it can and will happen to any service provider. The point is that in order to maintain business continuity, enterprises need to take responsibility for planning their outage contingencies.
HINDSIGHT: Amazon outage one year later: Are we safer?
The problem is that business processes, applications and computing infrastructure are too intertwined and dependent on each other. If the infrastructure isn't configured just right or is unavailable, the business process stops. The industry has made great strides in abstracting the physical computing infrastructure from the applications it supports. Amazon and VMware have created tremendous value and built businesses by abstracting (or insulating) applications and users from hardware diversity and failures.
However, the industry has only started to abstract the business process from the applications and infrastructure that supports it. To work around an Amazon EC2 outage, organizations really need to utilize more than one provider to avoid a single point of failure. Yet in order for the business to be successful at this there needs to be the ability to reroute and rerun the process in their own data center or an alternative service provider. This is where higher-level process automation comes in.
The recent outages at Royal Bank of Scotland, BATS Global Markets and others demonstrate the inability not only to abstract the process from the infrastructure but to see the interdependencies and the failures that plague complex IT systems as well. In those particular outages, it took minutes to fix the problem but days to find it.
Process automation that keeps track of the complex interdependencies between applications, infrastructure and business workflows can help identify, or even predict problems. Then in the case of an unavoidable outage, the business workflows would be rerouted to an available data center.
Most process automation done today is low level IT administrative tasks for provisioning servers, handling backup or startup routines, and generally doing infrastructure tasks that require little decision making that could affect the line of business. This is necessary and important, but not sufficient to preserve the user experience or business process integrity in the face of increasingly complex IT environments where, statistically, something is always failing.
Enterprises must step up their IT process automation to the point that they can manage business workflows not just servers or IT tasks.