As enterprises come to grips with Cloud Computing demands (both internal and external) the IT groups will soon realize that the Hybrid model is the “best fit” for the new Enterprise IT organization. This will also force a closer alignment with various business units and provoke a rethink of the costing models for IT. can IT really stay a coast center given the inevitable variable demand curve of Cloud Services? Enterprise IT shops will consider various vendors (E.G., Azure, HP, VMware, Amazon & others) in light of the matrix created by matching customers service type needs to flexibility of leveraging a vendors Cloud Service offerings to suit the enterprise’s complex business needs. the ease of entrance and exit will be the driving forces behind vendor selection not just cost but ease of achieving true operational excellence.
Finance, Corporate Strategy, Biz Units and IT will collaborate to determine which “flavor” of Cloud Services are needed. For example the SaaS, IaaS or PaaS models may all be needed in the view of the business objectives. The decision of what kind of service offerings to implement will drive IT’s customers to do a functional decomposition of existing applications and distil what services are used today. This will lead to an “applicability analysis” of which type of Cloud implementation makes good business sense. Some may choose from Cloud Platform as a Service, Cloud Infrastructure as a Service, Cloud as a Software Service model. These may also include convent “off ramp & on ramp” strategies to allow customers to switch as circumstances dictate. An example of the choices is illustrated below:
As enterprises with regulatory concerns/mandates migrate to the Cloud (Private, Public, or Hybrid) compliance with regards to privacy and security will ether be barriers or demand enabling technologies.
Tricks like leveraging encryption of data at rest while keeping active keys elsewhere will allow immediate use of the IaaS platform’s compliance methods and limit the application’s need to make drastic changes in code to accommodate compliance monitoring logic.
I have a controversial view that the new SaaS adoption rates will be served more by focusing on user benefits VS “tech-selling” buzzwords. A practical example of this would be that I believe the growth in numbers of the “boomer” generation is going to drive more customers to the SaaS/IaaS platform providers. E.G., MyGait below offers not only a computer system tuned to older user needs (magnification, large keys, etc.) but also a service program and financing that essentially signs up the buyer to a SaaS model by selling features and benefits they need.
A combination of color coding and Input Method Editor (IME) options is perfectly suited for the older user in the US and international community.
A good working example of this is the lighting fast adoption rate in Mobile TelCo of the Windows Phone & Android applications.
An example of leveraging Cloud Services is to deploy an application that services the healthcare industry by ultilizing the Infrastructure as a Service(IaaS) model E.G., Azure:
To deploy a Cloud-based Azure Platform meeting HIPAA regulations, all application code segments must be designed using a web-services model where database elements and application code running in the cloud publish secure streams
Windows Azure allows an organization to create virtual machines (VMs) that run in Microsoft datacenters. Suppose the organization wants to use those VMs to run enterprise applications or other software that will be used by customers. We can create a SharePoint farm in the cloud, for example, or run HIIPA data management enterprise HITECH applications. To make life as easy as possible for our users, these applications would be accessible just as if they were running in an cost intensive local datacenter.
The Enterprise offering the Cloud Services must follow these five rules in order to stay comliant with HIIPA: