5 Key Essentials of Cloud Workloads Migration

imageThe benefits of migrating workloads between different cloud providers or between private and public clouds can only truly be redeemed with an understanding of the cloud business model and cloud workload management. It seems that cloud adoption has reached the phase where advanced cloud users are creating their own hybrid solutions or migrating between clouds while striving to achieve interoperability values within their systems. This article aims to answer some of the questions that arise when managing cloud workloads.

Continue reading

Newvem’s April Webinar

image

Dear IAmOnDemand reader, I would like to personally  invite you to join an interesting webinar that will take place this  Wednesday, April 3rd. 

As part of my job at Newvem, I have assembled a power-house panel of some of the top thought-leaders in cloud computing to discuss the importance of a healthy cloud, focusing on cost efficiency, risk tolerance, and resource optimization.

The Rabbit and the Mole: the Web Developer and the Data Scientist

Six years ago I led Zarathustra as the company and product manager. We started this new company to help SMB companies to manage their sales, operations and accounting in one system. I was young and handsome but with not a lot of experience in regards to recruiting and employing web software developers.

It was obvious to us that we didn’t have enough capital to hire experienced developers and while searching for guys to help us with the R&D we realized that we could find great talented young geeks. These guys accumulated their experience by establishment of websites for their own purposes and habits such as movies, sports and dating sites. This always reminds me of the Facebook story which started with a super fast rabbit, Mr. Zuckerberg. At the start he actually created ”thefacebook” service using his own hands and keyboard spontaneously understanding the need to create a simple UI/UX, support operation scalability and demonstrate great value to the end user.

Continue reading

The Cloud Lock-In (Part 2): The Great Lock-In of PaaS

As we climb up the cloud layers scale, the complexity increases hence the vendor lock-in. PaaS as well as SaaS layers present stronger vendor lock-in than the IaaS layer. 

Did you read the 1st part on IaaS Lock-In ? The Cloud Lock-In (Part 1): Public IaaS is Great !

The PaaS vendor releases the “cloud applications’ developers” from the need to maintain the script or the database environments. The PaaS vendor takes responsibility of aspects such as the application deployment, the big data, scalability and availability by enabling features such as multi-tenancy and cluster management. The market is dominated by PaaS offerings like Google Apps Engine, Force.com, Heroku, Xeround, MS Azure, Engine Yard, Cloud Bees, Gigaspaces, Apprenda and others.

Click here to find more information about the PaaS Market.

PaaS is evolving to become the masterful approach towards “cloud software development”. When approaching PaaS, the IT organization should take in mind that there is a reasonable risk that it will quickly be tied to a single programming platform and will not be able to move its applications and data between vendors (PaaS or IaaS). One of the main key points for this discussion is the IaaS portability capability. Let’s first define these two types of a PaaS vendor: 

1 – Public PaaSThe public PaaS vendor offering includes the hosting platform. The  IaaS layer isn’t exposed to the PaaS customer. The customer doesn’t control the IaaS layer at all and the IaaS portability is limited only to the IaaS platforms which the PaaS vendor supports.

2 – Private PaaS: The private PaaS vendor delivers only the wrapper layer that enables the application deployment over an IaaS. The customer has full control over the IaaS including its portability.

Important Note: Currently there is a lack of good definition on that subject. You may think that there is a relation to the public or private IaaS so no ! there is no relation. The difference is that the private PaaS is a completely outsource model and build-it-yourself and it can be deployed on Public and Private IaaS. 

>  >  >  > Public PaaS: Your PaaS vendor chooses the IaaS for you

I found the following statements in an interesting debate between a MS Azure customer and an Amazon AWS customer. It was published on GigaOM this month and I find it appropriate for the PaaS lock-in discussion:

“Getting stuck in a single framework like .NET where there is only one “provider” for .NET tools can be a huge hindrance in any future decisions you make as a company. Microsoft (and Azure as default) seems to be all about lock-in.  Lock-in on the operating system, lock-in on the language platform, as well as lock-in on the Azure services. Also, many companies do have to solve big compute problems that Java, unlike .NET, is well positioned for. While many larger companies don’t have to be as concerned with lock-in — this is a very scary thought for most start-ups that need a clearer longer-term cost structure.” 

Neither Microsoft nor Amazon are going away anytime soon. I would make a decision based on one thing and one thing only — bleeding edge capability and lock-in. “

The great debate: Windows Azure vs. Amazon Web Services

> > MS Azure
These debate’s statements above brought me to search and find for more materials on MS Azure platform in regards to vendor lock-in:

“While every platform has some degree of lock-in, you should look for a partner that offers the ability to move your application into your own data center without completely re-writing it. Avoiding lock-in entirely probably isn’t possible, but making an effort to minimize it up front makes sense. “

I found this statement in the article “The benefits and risks of cloud platforms” written by David Chappel and published on the MS Azure site. I definitely don’t agree with Chappel and I think it is ridiculous (I thought alot before using this word..) to think that after investing in shifting to the cloud (not as an additional hosting), a company will consider moving back to its premise (Disclosure: `I Am OnDemand` is not sponsored by Amazon AWS or any other MS competitor. ;)). For “MS ISV” that is already locked on Microsoft platforms I can just say that the shift to the cloud might be a good point to re-think and re-plan its infrastructures including its lock-ins (I recommend to check Apprenda as an additional option to help with cloud enablement).

> > Force.com

As well as MS Azure the same strong lock-in should be mentioned when discussing Force.com, again the lack of IaaS portability capability and the “closed source” programming language and database. 

Salesforce.com bills Force.com as “The leading cloud platform for business apps.” It is definitely not for me, though. The showstopper: infrastructure portability. If I develop an application using the Apex programming language, I can only run in the Force.com “cloud” infrastructure.” Read a bit more about Force.com lock-in on Mike Gualtieri his Forrester blog post “May Force.com Not Be With You by”

Force.com Vs. MS AzureRead this discussion on Quora

> > Heroku

Understanding that “cloud apps developers” find lock-in as a major issue as well as the rising of Rubi on-Rails among those developers, led Saleforce to acquire Heroku.The Heroku PaaS supports standard interfaces for web services such as HTTP, JSON and XML. They also support open source languages such as Java, Ruby, PHPFog and databases such as PostgreSQL and MySQL. Heroku has been extended to support Java and also been integrated with Salesforce’s Database.com. Salesforce did a clever move that expands its PaaS capabilities. It is great that presenting an open source platform strengthens the company market positioning as one of the world’s cloud and PaaS giants.

Heroku Vs. Engine YardRead this discussion on StackOverFlow

> > Xeround

Another interesting player in the market is Xeround which delivers database as a service. Following my conversation with Xeround CTO, Mr. Avi Kapuya it seems that the competition is more aggressive than in the traditional world where the giant software vendors hold most of the market for run-time script and DB platforms. I asked Mr. Kapuya about Xeround lock-in and he responded that: 

“Lock-in is a subject we take seriously so that customers don’t want lock-in is a basic premise. We make sure to provide our customer the flexibility by supporting MySql interface. The user can easily import his data back to his end any time straight from our site. The same way around a new user can simply upload the data to Xeround platform and continue to work with his ordinary MySql development tools”.

In regards to IaaS portability Kapuya added that:

We consider the portability between public clouds as a service. We run our platform on several IaaS such as AWS and Rackspace and we give our customer the option to select the preferable one. Once a customer asks to move his database from Amazon AWS to RackspaceXeround will move the database to Rackspace, and will shutdown the Amazon database accordingly. Furthermore, our prices are derived from the IaaS vendor prices”

The IaaS portability presented by Xeround differs them from the other vendors I mentioned above. Further more I think that this is an important benefit for Xeround’s customers as they can better trust Xeround with its availability and future options in regards to cloud interoperability and federation.

What are cloud interoperability and federation? Check I Am OnDemand terminology page.

>  >  > > Private PaaS: IaaS at your choice

The other side of the PaaS lock-in story is the private PaaS. Private PaaS vendor provides the application’s “cloud wrapper” and solves issues such as service deployment and scalability. Those can be achieved by enabling multi-tenancy enablement, clustering management, database distribution etc. Traditional ISVs specifically can use private PaaS help with their shift to the cloud. The private PaaS can be deployed on private as well as on public IaaS.

> > Cloud Foundry by VMWare

Discussions on PaaS lock-in should include Cloud Foundry. Cloud Foundry includes SpringSource Framework, an enterprise Java programming model that VMware picked up in its August 2009 acquisition of SpringSource. On April this year VMWare announced Cloud Foundry initiative to support multiple frameworks, multiple cloud providers and multiple application services all on a cloud scale platform.

Watch the Cloud Foundry webinars on the PaaS playlist on I Am OnDemand YouTube Channel

Proud on their PaaSVMWare opened the site DeveloperRights.org and listed the cloud’s developer rights that will help avoid lock-in. I vote for the following:

“The Right to Cloud Portability – The choice of clouds shall not be infringed, today or in the future. If an application works in one cloud or on our laptop, it should work in any cloud and not require learning a new deployment model. “

>  > GigaSpaces

In the private PaaS market you will also find Gigaspaces. I had the privilege to meet the company founder and CTO Mr. Nati Shalom who is a well known and appreciated cloud blogger in the market. I strongly recommend checking his personal blog which presents deep technical analysis of PaaS issues. Gigaspaces was founded in 2000 and over the years it struggled with bringing its PaaS vision to the market.The rise of cloud computing and the growth of the market helped Gigaspaces with its business growth. In regards to the differences between public to private paas Shalom said:

“Another difference between PaaS vendor such as Gigaspaces to vendors such as Azure is that the former provides a solution contrary to the latter that provides a product and tools. Using Azure you still have alot to invest in order to have a working application, as for example perform big data aggregations to eventually generate business analytics.”

Gigaspaces invested 3 years in developing an abstraction layer that enables compatibility with a private environment or a specific public IaaSGigaspace Cloudify product enables ISVs to deploy its platform on on public or private cloud infrastructure. Answering the vendor lock-in issue Shalom said: 

“We don’t care what are the application containers including the run-time and database. Our abstract layer wraps the app stack without any changes to the app run-time. Actually it contains number of recipes that defines an application from outside. The layer also holds list of metrics and the relevant SLA rules. For each metrics there is a threshold and an action. 

> > Apprenda

Another vendor that I talked with in regards to private PaaS lock-in is Apprenda. Following my conversation with Sinclair Schuller, the company CEO and Co-Founder, I find that the cloud lock-in issue is not only the cloud customer consideration but can be served as a business initiation incentive. Apprenda is specialized with public cloud enablement and support for ISVs and enterprises that work with Microsoft development platforms such as MS .NET, SQL Server, ASP.NET & Silverlight. Naturally the main competition of Apprenda is with MS Azure. It is a fact that ISVs that don’t want to be locked in Azure infrastructure will find Apprenda appealing. Contrary to the traditional world and following developers’ experience it is a fact that lock-in has a great impact on the cloud decision considerations. Apprenda clearly proves that the cloud lock-in issue can actually generate new business. “Which Part of the Public vs. Private Cloud Elephant Are You Touching?” by Schuller

> > > > Conclusion

When selecting a PaaS solution, the lesson is that you should always look for the option, if only in theory, to move to another provider without having to completely rewrite your application code. In order to decrease the lock-in risks, you must think carefully about your application business logic when implementing so when conversion is needed you will be able to use the data and the app structure from one platform to re-build the apps in another. Read more on how to select a PaaS provider.

“So what will be the best choice for the IT organization?” I asked Shalom. He answered: 

“The trade off is between simplicity and control. If you want to get control you will pay in complexity and skills and if you want simplicity you will need to compromise on your control. The space in between those two is filled with the customer urge to get the control and the simplicity. The balance can be achieved by a hybrid perception. The IT organization should be able to adopt both concepts, use the vendors like Gigaspaces for its mission critical applications and vendors such as Heroku to deploy the “lighter” applications such as the mobile extensions for the enterprise apps”

In his CIO blog post “Cloud Computing: What You Need to Know About PaaS, points Bernard Golden on “the things IT leaders should think as they begin to evaluate their PaaS options”. It is not surprising that lock-in is the first thing in his list:

I’m less disposed than many to see lock-in as purely negative, as in my experience organizations embrace lock-in because it provides significant benefits”

Following my research and my mantra about the open cloud eco-system world I tempted to say that public PaaS is my preferable option as it also includes great business benefits such as time to market and small investment in comparison with the private PaaS. I also tend to agree with Shalom in regards to his hybrid PaaS perception.

The PaaS vendor must recognize the “open cloud world” with its business benefits as it extends the vendor’s eco-system as well as the amount of new opportunities. Thanks to the traditional software giants (i.e MS, Oracle, etc.) and the open source evolution, IT organizations are much more experienced with choosing their vendors. Lock-in must be positioned higher in the PaaS vendor evaluation considerations list and weak lock-in is a huge benefit.

Part 3 will discuss SaaS vendor lock-in

Stay tuned with I Am OnDemand.

The Cloud Lock-In (Part 1): Public IaaS is Great !

It always good to start with Wikipedia’s definition as it helps to initiate a structured discussion, here is Wiki’s definition for Lock-In:

“In economics, vendor lock-in, also known as proprietary lock-in or customer lock-in, makes a customer dependent on a vendor for products and services, unable to use another vendor without substantial switching costs. Lock-in costs which create barriers to market entry may result in antitrust action against a monopoly.” Read more on Wikipedia

Does the cloud present a major lock-in ? Does the move create substantial switching costs?

“Yes !” is the common answer I hear for those questions. In this article I will debate it basing my findings on real cloud adoption cases.

Generally in terms of cloud’s lock-in, we face the same issues as in the traditional world where the move includes re-implementation of the IT service. It involves issues such as data portability, users guidance and training, integration, etc.

“I think we’ve officially lost the war on defining the core attributes of cloud computing so that businesses and IT can make proper use of it. It’s now in the hands of marketing organizations and PR firms who, I’m sure, will take the concept on a rather wild ride over the next few years.”

The above statement I bring from David Linthicum’s article “It’s official: ‘Cloud computing’ is now meaningless”. Due to my full consent with Linthicum on that matter, I will be accurate and try to make a clear assessment of the cloud lock-in issue by relating each of the three cloud layers (i.e. IPS aaS) separately.

In this part, I will relate to the most lower layer, the IaaS lock-in.

It is a fact that IT organizations take advantage of the IaaS platforms by moving part or even all of their physical resources to the public clouds. Furthermore, ISVs move at least their test and development environments and making serious plans to move (or already moved) part of their production environment to the public clouds.

Read more about shifting legacy systems to the cloud by Ben Kepes

Discussing with a public IaaS consumers, it always come to the point where I ask “do you feel locked on your cloud vendor ?” most, if not all of the companies’ leaders claim that the public clouds’ values (on-demand, elastic, agility,ect) overcomes the lock-in impact so they are willing to compromise. As a cloud enthusiastic it is great for me to see the industry leaders’ positive approach towards moving their businesses to the cloud (again too general – any of them refer to a different layer). I do not think that the lock-in is so serious.

For sometime this claim sounded pretty reasonable to me though on second thought I find that the discussion should start from a comparison with the traditional data center “locks”. Based on this comparison I can already state that one of the major public cloud advantages is the weak lock-in, simply because you don’t buy hardware. Furthermore, companies that still use the public cloud as an hosting extension to their internal data center, don’t acquire new (long term or temporary) assets that they can’t get rid of without having a major loss. In regards to its lock-in the public cloud is great !

Another important explanation related specifically to Amazon AWS products which support SaaS scalability and operations. Smart SaaS architect will plan the cloud integration layer, so that the application logic and workflow will be strongly tied with the underlying IaaS capabilities such as on-demand resources auto provisioning.

Read more about the relationship between web developers and the cloud

For example, the web can use the cloud integration layer to get on-demand EC2 resources for a specific point when a complex calculation occurs. In a superficial glance, the fact that the cloud API used as a part of the application run-time script holds an enormous lock-in risks. I disagree and let me explain why.

As a market leader, Amazon AWS will be (already is) followed by other IaaS vendors. Those will solve the same scalability and operational issues by the same sense and logic of AWS. Basically this means an evolution of IaaS platform standards. Smart cloud integration layer will enable “plug & play” a different IaaS platform or even orchestrate several in parallel. To strengthen my point I bring as an example several cloud start-ups (solving IaaS issues such as governance, usage and security) that developed their product to solve issues for Amazon AWS consumers and seriously target support of other IaaS vendors’ platforms such as Rackspace cloud and vCloud. In regards to lock-in the public cloud is great !

The IaaS vendors in the market recognize the common lock-in drawback of moving to the cloud. Vendors such as Rackspace brings the OpenStack which is a cloud software platform, so cloud vendors can build IaaS solutions upon it. Rackspace showing off on their blog site –

OpenStack™ is a massively scalable cloud operating system, powering the world’s leading clouds. Backed by more than 50 participating organizations, OpenStack is quickly becoming the industry standard for public and private clouds. Read More

It should be noted that applications and data switching between clouds is still complex and in some cases not feasible though believing in the public cloud’s future comes with understanding of its weak lock-in and will lead to visionary and long term strategic plans.

What about the private IaaS ?

Following my on going research on what is the best cloud option (i.e public, private or hybrid), I found that outsourcing the IT environment to a private or an hybrid includes a major lock-in. Implementation of a private or an hybrid cloud includes lots of customization, hence lack of standards. Private and Hybrid clouds have their benefits though lock-in is not one of them. The contract with the vendor is for 3 to 5 years at least (a data center’s typical depreciation period) on a non standard environment leads to an extreme, long term lock-in in terms of the “on-demand world”.

In order to decrease lock-in the IaaS consumer must prove the organization need for a private cloud by planning strategically for long term. Besides the ordinary due diligence to prove the vendor strength, the contract must include termination points and creative ideas that can weaken the lock-in. For example renewal of initial contract under re-assessing of the service standards, costs and terms in comparison with the cloud market, including the public one. The private cloud vendor must prove on-going efficiency improvements and costs reductions accordingly.

In his article Keep the ‘Cloud’ User in Charge”, Mark Bohannon, VP at Red Hat, Warns:

by vendors to lock in their customers to particular cloud architecture and non-portable solutions, and heavy reliance on proprietary APIs. Lock-in drives costs higher and undermines the savings that can be achieved through technical efficiency. If not carefully managed, we risk taking steps backwards, even going toward replicating the 1980s, where users were heavily tied technologically and financially into one IT framework and were stuck there.”

Some of the private cloud offering today have similar characteristics as the traditional data center, to me it seems that the former comes with a stronger lock-in impacts. In case of an IT transition companies who decide to go that way should expect a considerable switching costs and long term recovery of their IT operations hence of their business.

The second part will discuss the cloud lock-in characteristics in regards to the SaaS and the PaaS layers.

Developers are from Mars

The three layers of cloud computing IaaS, PaaS and SaaS occupy the headlines with significant capabilities undergo continuous improvement to host services in the cloud. This growing market is slowly changing so that offered services will become generic. The current evolving struggle is the deployment and management of SaaS applications in the cloud, Gartner calls this cloud market portion SEAP (Software Enabled Application Platforms). We will dare to say that developers are from Mars and cloud providers from Venus, let us explain in detail why.

SaaS application developer builds the application architecture structure including the database system, the business logic and the user Interface. The software developer (or the SaaS vendor for that matter) invests on building these main three infrastructure cornerstones in order to bring life to the business idea and launch a new on-line service.

Traditional software delivery puts the responsibility of deployment and maintenance in the hands of the customer. In contrast, the SaaS model key includes building the infrastructure wrapper that allows meeting the requirements to deliver it as a service. The change from the licensing model is that the SaaS vendor (the developer) is also the integrator and the responsible to support standards by adopting technologies which makes the software as a service.

The most popular example is the support of multi-tenant. This feature enables the scalability to perform extensive SaaS sales and effective maintenance on the  non-physical infrastructure.  The virtual infrastructure brings higher level of complexity which requires additional maintenance means. This complexity intensifies as the number of customers grows, hence the demand for more cloud capabilities and resources.

Developers use existing frameworks that enable a short and efficient development such as .NET provided by Microsoft or Ruby on Rails brought by the open source world. Software architects already understand that the application multi-tenancy is a part of the system infrastructure to enable scalability, but is the that enough to make an application as a service? the answer is no, there are more considerations the developer need to bear in mind when planning the architecture of software as a service.

Why Multi-Tenancy ?

In order to plan the development of a robust and automatic scalability, the software architect must understand the cloud dynamic nature that is to say the basic option to start and shut down resources automatically. The software vendor should pick the IaaS vendor as part of the initial development step, learn the IaaS platform’s API capabilities and make sure that the development roadmap includes also a tight integration with the cloud facility. The IaaS platforms offered are still young and automation deployment is still limited due to infrastructure barriers. Most of the IaaS platforms doesn’t provide convenient tools to deploy the application, therefore the SaaS vendoר is forced to invest in purchasing existing tools or even implement independently. Today we still see vendors that are not aware of these requirements as they are not pure application but operations oriented.

Learn how to Scale IT – an article by CloudInsights.org

Check out I Am OnDemand terminology page and learn more about the four levels of Multi-Tenancy.

Another aspect in the SaaS development discussion is the option to build the system on a PaaS. There is a good number of PaaS manufacturers that offer products enable development capabilities as a service and by that solve the developer’s need to maintain a scalable service as described above. We can divide the this group of products to following two categories: 

  1. Objects as a service – force.com is an example for such vendor. The developer will buy the option to use the out of the box software objects to implement a new application. 
  2. Runtime and database as a service – here we can mention platforms as Heruko, Google Apps and MS Azure.

Gartner predicts a growth in the amount of platforms that provide the wrapper for the web development of new and existing application. These platforms already have taken a significant part in the cloud evolution. The number of PaaS providers grows while the existing vendors continue to extend their on-demand tools portfolio, enabling a wide range of services for operation, management and distribution of SaaS applications.

Learn more about the PaaS market

Besides the actual system scalability issues presented here, there are much more “developing for the cloud” considerations such as integration, develop for resources’ optimal utilization and SaaS development with the fast changing clouds’ platforms. Check out Cloud development: 9 gotchas to know before you jump in, an article brought to you by InfoWrold.

The relationship between the actual application development and the operational side of the application becomes stronger. While the SaaS vendor’s board should think on all cloud adoption strategic aspects, the vendor’s software architect as well as the product manager should think “out of the application box” to be able to deliver their product as a service.


Special thanks for Amit Cohen who raised this discussion and took a part in composing this article. Cohen is an experienced  SaaS & Cloud computing consultant for the enterprise who held executive positions at several international software vendors over the last 10 years.


`I Am OnDemand` Discussion: Cloud Computing – Is this a Revolution or just an Evolution ?

Three months ago I started this LinkedIn discussion and I keep getting comments about it. People might say that it is just a defiant question for marketing purposes. I say that this question raises many thoughts and opinions that helps marking the strategy of an IT organization. I invite you to read the following comments that can bring you to think a bit more about your current On-Demand strategy and approach.

> > > > > Answer #1: Just a Buzzword

It’s a buzzword. This is a 70’s-80’s technologies evolution. Remember mainframes, VM/370, per-time payments when using machine. Just another evolutionary loop, development of already existent technologies. In my opinion Cloud computing is an evolution. Started with the revolution of Grid computing, then Utility computing, SAAS computing and now it finds its preliminary conclusion in Cloud computing. Thus no it is not a revolution, it is a revolutionary step in the evolution of what is now called Cloud computing. This is just a good name for number of technologies that was ready years before than customers are become ready for it and useful software was written. Many companies added “Cloud” to the titles of their solutions. Any site can be marked “Cloud ready” or “SaaS solution” 🙂 It means that it’s only marketing. This all is possible because people don’t know what Cloud is in details; sellers often talk about it as about some magic. You can use Magic instead of Cloud; meaning stays the same – marketing.

> > > > > Answer #2 : Depends! From the technology perspective: Evolution and from the business point: Revolution

“From a technology point of view I am pretty positive about categorizing it as evolution and not even sure if representing a significant step; from a business standpoint however I think there is much more value in the concept. I believe that Cloud Computing introduces a capability to rapidly map dynamic changes in the business models that is kind of revolutionary

“My observation is that “cloud” is a description of how IT is supposed to work from a business perspective: flexible, available, efficient (lower cost), secure, dynamic, responsive, etc. If you are an IT specialist, the technology is evolutionary, but the thinking may be revolutionary.”

“I tend to think that the cloud computing Revolution will transform the way all businesses interface include enterprises with technology and communications, and marks the next wave of the fundamental changes that the evolution of the internet has already brought about the Tera Play

> > > > > Answer #3: IaaS just an Evolution. Massive Scaling, supported by PaaS and SaaS, is the Revolution.

“I’ve seen global Trading and risk systems, (30,000 node compute grids, nano second trading platforms), some true cutting edge platforms. And this is really a complete transformation of IT. If you’re thinking just IaaS then it’s just evolutionary. True SaaS and PaaS is a revolution. The fact that Salesforce (and the force.com platform) can deliver millions of users and 97500 customers on a single multi-tenant platform with three major upgrades per year. That’s the power of the cloud. Giving a small 10 user non-profit the same reach and scale as a multibillion dollar organisation. The cloud. No admin or maintenance, pure development and software business process IP. What other technology can scale from 1 to 100,000 users. It can take much less than 10% of the traditional development to build a SaaS app compared to traditional platforms. Cheaper , faster AND better . That’s a revolution.

“The prior comment reflects a deep misunderstanding about what timeshared (outsourced) mainframe computing was all about. Cloud is just another swing in the pendulum. The business owners in the 60’s were right: why should we buy and maintain our own computers when we can better spend the money by renting the computing resources from somebody who knows how to take care of all that “stuff”? It’s not new. We’re just coming around to the fact that PC computing set the industry back 40 years and we’re now where we would have been if PCs had not taken 25 years to “grow up”.

As amorphous as this question might be, the analogy to mainframes is highly misplaced and not very useful. Among other defining characteristics, cloud services allow software developers to control infrastructure resources programmatically. This means that applications specifically designed for cloud environments can bypass the historically slow and error prone layer of IT administrators that maintain computing resources through largely manual, error prone processes. Companies that use such functionality to enable auto-scaling, such as Netflix, are doing so without the need to invest capital into stranded computing capacity that may or may be fully subscribed. I’ll leave the ever so important question of evolution vs. revolution to you, but explain to me how the Netflix development team could have replicated their

“Revolution – Cloud is a disruption of everything internet and application as we know them. The very large infrastructure and service vendors are racing to rework their offers and slow things down to keep their competitive advantage. Revolutions are messy – like a massive earthquake or coup d etat. Evolution is what you study afterwards when learning which creatures adapted and which went extinct.”

> > > > > Revolution by Wikipedia takes place in a short period of time

“According to the Wikipedia definition: A revolution (from the Latin revolutio, “a turnaround”) is a fundamental change in power or organizational structures that takes place in a relatively short period of time. So how this aligned with the “Cloud Computing Revolution” that doesn’t seem to come up in a short period of time?… I remind you that Amazon started its AWS 11 years ago… ” I asked

“Ofir – most revolutions have a long lead up time where the angst ferments underground and bursts out in a moment of time when the underlying ability to organize action is catalyzed by some event – Egypt for example (mobile devices & Facebook). Think of the internet revolution in 1995-1997. The internet was slowly building out (DARPA net, etc) with organization by the scientific/defense communities and catalyzed by Tim Berner Lee public gift of http/html. The corporate world was seeking a way to collaborate beyond the bonds of one company’s offer, like IBM & MSFT. Within two years the Internet exploded into the corporate world, literally revolutionizing the ways companies marketed themselves. The coup was over when Bill Gates announced that Msft was an Internet company and Netscape dropped $25 in a day!”

This month Christian Verstraete, HP’s Chief Technologist also raised this question in the CIO magazine. In his post he writes:

“One of the questions that came on the table was whether cloud computing is a revolution, a paradigm shift, or not. I’d like to answer, it’s both.

I say that the cloud computing is Evolving faster to become a Revolution,

what do you think ? Join the discussion