Skip to main content

How hot is cloud Computing?

In previous posts such as Cloud Computing: Hype, Vision or Reality?, Hyped Cloud Technologies, PAAS is not Mainstream yet, SaaS is going Mainstream, Future applications: SaaS or traditional? I discussed Cloud Computing.


Recently I read Joe McKendrick's interesting article titled:Cloud Computing Market Hot, But How Hot? Estimates are All Over the Map

Joe's views and predictions are similar to mine. However, he base his opinions on actual survey done by him, as part of his work with Unisphere Research/Information Today Inc and on leading Analyst firms predictions.


I recommend reading Joe's article. 
The following bullets quote few highlights:



  • Market Research Media,cited in the Bloomberg report, says the cloud market will reach $270 billion in 2020.
  • Forrester is a tad less optimistic, predicting last year that the market will hit $241 billion by that time. 
  • Research firm IDC says the market will hit about $55 billion by 2014.
  • The larger companies in the survey are most inclined to be supporting their own private internal clouds. Close to half of the companies with workforces of greater than 10,000 employees (45%) have private clouds in production or in limited use. By contrast, only 11% of the mid-size companies in the survey have such efforts underway.
  • Public cloud adoption, on the other hand, is most pronounced among the smaller companies in the survey. One-third of companies with 1,000 or fewer employees use public cloud services, versus 19% of the largest companies in the survey.




Labels:

Comments

Avi Rosenthal said…
LinkedIn Groups

Group: ZapThink Architect Group
Discussion: How hot is cloud Computing?
Cloud is Hot. Period. The question really boils down how the client firm can best utilize it. This is often a function of the question "do you have a need and a budget for IaaS". This is typically driven by the amount of sensitive personally identifiable data your firm needs to collect. If you don't have security or compliance requirements that would require you to collect and/or store lots of SPI data [which, outside of financial and healthcare professionals, is not frequently the case for small businesses], then you will frequently choose to go with a SaaS solution - whether COTS or Developed in House and hosted.

If however, you DO collect a lot of that type of data, then the options for SaaS become a great deal more limited -- at least at the moment. At that point, you must begin to consider using internal systems to store that data, and when thinking strategically, this will mean IaaS. And, conversely, being responsible for the safe storage of this information, a customer firm will typically error on the side of caution, rather than open themselves up to a security or compliance failure risk.
April 27, 2012 at 10:18 PM
Post a Comment

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...
16 comments
Read more

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...
11 comments
Read more

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...
8 comments
Read more