Lock of cloud-locked public paas and private PAAs

PAAs vendors provide the development environment for cloud applications and the scripting or database environments that need to be maintained, and provide users with a variety of tasks, such as application deployment through multi-tenant and cluster management, large data, scalability, and availability, and the PAAs market has been implemented by Google App Engine, Domination of Force.com, Heroku, Xeround, Microsoft Azure, Engine Yard, Cloud Bees, Gigaspaces, and Apprenda.

It organizations should be aware that using a PAAs platform will allow you to quickly be controlled by a single programming platform, when applications and data are difficult or impossible to migrate to other PAAs or IaaS vendors. This is a risk and the focus of the debate is on the portability of IaaS, so let's look at the definitions of the two PAAs vendors first.

1. Public PAAs: Public PAAs vendors provide services including managed platforms, the IAAS layer is not exposed to PAAs users, users cannot control the IaaS layer, and IaaS portability is limited only by the IaaS platform supported by the PAAs vendor.

2. Private PAAs: Private PAAs vendors only provide packaged layers, allowing applications to be deployed on IaaS, and users have complete control over IaaS, including its portability.

Important: There is no good definition of this topic right now, and you might think there's a connection between a public IaaS and a private IaaS, but there's really no relationship between them, and the difference is that a private PAAs is a completely outsourced model that you can build yourself, control, Can be deployed on public PAAs and private IaaS.

Public PAAs: Your PAAs vendor chooses IaaS for you

The interesting debate between Microsoft Azure and Amazon AWS users in Gigaom this month--paas locking discussions.

"Stuck in a framework like. NET, as a company, and in future decisions, Microsoft has achieved great success in locking users, locking the operating system, locking the language platform, this time trying to lock down Azure services, and many companies must address the Java location, Many big companies have yet to think about lock-in issues, which is very scary for many startups because they need a clear long-term cost structure.

"Neither Microsoft nor Amazon will disappear anytime soon."

Microsoft Azure

The debate above made me want to search, and eventually I found more information about Microsoft Azure platform lockdown.

"While each platform has varying degrees of lock-in, you should look for a partner who has the ability to provide more applications to your data center without rewriting those apps and avoiding locking altogether is not impossible, but minimizing it is more relevant."

Found above in the article "Benefits and risks of cloud platforms" written by David Chappel, published on the Microsoft Azure website. I disagree with Chappel, and I think his idea is a bit ridiculous, and for Microsoft ISVs, they do have been locked on the Microsoft platform, only to say that moving to the cloud might be a good idea, a chance to rethink and plan its infrastructure, and not lock down the problem.

Force.com

When it comes to force.com, it has to be said that its locking strength, like Microsoft Azure, lacks IaaS portability and uses a closed-source programming language and database.

Salesforce.com is positioning force.com as a leading enterprise application cloud platform, but I disagree because it does not have infrastructure portability, and if I develop an application that uses the Apex programming language, I can only run on the force.com cloud infrastructure.

Heroku

Cloud application developers found that locking was a major problem for them, so Ruby on Rails was reused among these developers, so Salesforce acquired the Heroku,heroku PAAs support standard Web Service interfaces, such as HTTP, JSON, and XML, also supports open source languages and databases, such as Java, Ruby, Phpfog, PostgreSQL, and Mysql,heroku, which have been extended to support Java, Also integrated with Salesforce's database.com, Salesforce clearly shows that it wants to expand its PAAs capabilities, and the open source platform once again proves its greatness and strength.

Xeround

Another interesting company in the market is Xeround, he launched the database as a service, after my talk with Xeround CTO Avi Kapuya found that the competition is more intense, traditional database manufacturers occupy a large number of markets, I asked Kapuya about the xeround locking problem, He replied as follows:

"Locking is a problem we take seriously, users do not like to lock, through the MySQL interface support, we prove to the user xeround flexibility, users can always from our site to guide the data, for new users is also very simple, they can upload data to Xeround platform, Continue to work with their previous MySQL development tools.

With regard to the portability of IaaS, Kapuya has made the following additions:

"We think seriously about portability between public clouds, we run our platforms on a variety of IaaS, such as AWS and Rackspace, our customers have the opportunity to choose their preferred platform, and if a user asks to move his database from AWS to Rackspace, Xeround will comply, and our price is derived from the price of the IaaS manufacturer.

Xeround's IaaS portability is different from that of other vendors, and I think xeround customers can get more benefit from the Xeround advantage in future cloud interoperability and syndication.

(Responsible editor: The good of the Legacy)