I believe that this is the year when the enterprise will find its way to the cloud.
The mega Internet sites and applications are the new era enterprises. These will become the role models for the traditional enterprise. IT needs remain the same with regards to scale, security, SLA, etc. However, the traditional enterprise CIO has already set the goal for next year: 100% efficiency.
The traditional CIO understands that in order to achieve that goal, IT will need to start and do cloud, make sure that IT resources are utilized right, and that his teams move fast.
Over the last year I had endless conversations with companies that strive to adopt the cloud – specifically the Amazon cloud. Of those I met, I can say that ClickSoftware is one of the leading traditional ISVs that managed to adopt the cloud. The Amazon cloud is with no doubt the most advanced cloud computing facility, leading the market. In my previous job I was involved in the ClickSoftware cloud initiative, from decision making with regards to Amazon cloud all the way to taking the initial steps to educate and support the company’s different parties in providing an On-Demand SaaS offering.
As befitting any great online vendor, Amazon cloud product guys listen carefully to their market targets and ensure fast implementation and delivery to satisfy their needs. It is clear that Amazon cloud is eager to conquer the enterprise market, as I already mentioned in my past post, “Amazon AWS is the Cloud (for now anyway)”.
Every day I talk, write and comment about the “Cloud”. Every time I mention the cloud I try to make sure that I add the name of the relevant cloud operator, “Rackspace Cloud, “MS Cloud” (Azure) or “HP Cloud”. Somehow all of these cloud titles don’t right to me – it seems the only title that really works for me is the “Amazon Cloud”. In this post, I will elaborate about the competition in the IaaS market and I will explain further why I think this is so.
Last week I attended one of the most popular cloud technology conferences in the world – CloudConnect. The CloudConnect conference started about four years ago. Attending the event gave me a clear understanding of the market maturity and evolution rhythm. Check out the following sections for the main points on what I heard and learned:
The underlying infrastructure performance, round trip time, bandwidth, caching and rendering are to be counted as the major features of an online service performance. In an interesting presentation by @joeweinman (known by his famous “Cloudonomics” theory), it was claimed that latency holds the greatest weight among these faetures. I encourage you to check out his new research – As Time Goes By: The Law of Cloud Response Time presents some good formulas, methods and considerations with regards to online services’ performance and latency (including simple facts, for example, that people tend to prefer selecting from fewer options on an online page – so you can have less content on a page and achieve a better browsing performance).
Last week I was invited to the HP Tech Day in HP’s campus in Houston to learn and hear more about the giant’s cloud offering. I appreciate HP and Ivy very much for the invitation and for a great event where I was able to learn more and see these clouds in real. I had the privilege to meet savvy and professional guys. It is always great to see people who are enthusiastic on their jobs and are proud of their company. Let me share with you HP’s cloud from my point of view.
This is the third and last post in regarding the cloud lock-in. In the first and the second parts I covered the vendor lock-in of IaaS and PaaS. The appealing registration and the low cost overwhelm the new SaaS consumers that often makes them forget that eventually the service will become something they just can’t live without. What will happen if one day your SaaS vendor goes out of business ? In this post I will try to cover the threats and the actions the enterprise should take in order to lower the level of the SaaS lock-in risk.
> > > How does the lock-in of a SaaS application differ from a traditional on-premise application?
SaaS use is actually the consumption of servers, operating systems, middle ware, network connections and more. Switching a SaaS vendor is much simpler as these are not located in your site – shifting to another vendor mainly includes migration of the data without the hassle of ripping and replacing the full app stack. This cheerful answer also provides a less costly and less complex switch than the painful effort and the risky investment of moving an on-site software.