The five major platforms that enterprises must understand are service products

Absrtact: Dot Cloud is by far the most attractive platform for service products. It is of great concern, especially given the ambitious vision it has put forward.

If everyone's application needs ruby resources and some support for node.js, Heroku should be the first choice to override other platforms, the service offerings. While its owner is Salesforce.com (which is also a big annoyance for VMware), Heroku is still worthy of the title of the Generation Cloud platform. We don't have to worry about server workloads or the scalability of applications, Heroku is simply introducing our own and our customers ' applications into the cloud platform.

Clearly, the biggest weakness for Heroku is the lack of functionality. We can only hope that the Salesforce company, the Heroku project will be able to get more resources to enhance its scalability, including the introduction of Java,. NET, Python, C, + + and other types of enterprise users may use the programming language and stack applications. Heroku in some ways is similar to Apple's platform, the service product approach: It focuses on solving a class of problems and is very, very much in place; If this is the case, we often seek solutions from VMware companies.

Cloud Foundry has the biggest heritage advantage in the list of products, but in the current market it is playing the awkward dark horse role. In other words, whether the future of Cloud foundry is bright depends entirely on how VMware companies shape it.

The guiding ideology behind Cloud Foundry is great: Integrate Java, Ruby, and Node.js into the same platform for wide availability. Unlike the Heroku hosted by the Yu Yun platform, Cloud Foundry is designed to run on top of the user's data center. As a result, your enterprise-class spring applications can be migrated to this modular platform and deployed to data centers that require cloud foundry functionality. And with the support of SpringSource behind the platform, you can all be confident that Java stack apps will become faster, smaller, and more optimized.

There are, of course, some doubts about the platform. But these doubts are unfounded, and VMware has made little response. Cloud Foundry was only a theoretical one, but VMware first brought it into the bag a few days before the acquisition of SpringSource. It is rumored that the potential value of the Cloud Foundry project has led to a wavering VMware firm's determination to buy SpringSource.

However, the takeover event was old news two years ago, and cloud foundry still did not appear in the full version of the world. The truth seems to be that VMware, after completely missing Heroku, has instead decided to revise the plan to create a rival that is strong enough to compete with Heroku. Once the cloud foundry and its MicroCloud desktop systems are deployed in a test environment, a new, practical and powerful product will be born. Please pay attention to the new version of MicroCloud that will be launched later this summer or to cloud Foundry's own site.

Cloud Foundry has the biggest heritage advantage in the list of products, but in the current market it is playing the awkward dark horse role. In other words, whether the future of Cloud foundry is bright depends entirely on how VMware companies shape it.

The guiding ideology behind Cloud Foundry is great: Integrate Java, Ruby, and Node.js into the same platform for wide availability. Unlike the Heroku hosted by the Yu Yun platform, Cloud Foundry is designed to run on top of the user's data center. As a result, your enterprise-class spring applications can be migrated to this modular platform and deployed to data centers that require cloud foundry functionality. And with the support of SpringSource behind the platform, you can all be confident that Java stack apps will become faster, smaller, and more optimized.

There are, of course, some doubts about the platform. But these doubts are unfounded, and VMware has made little response. Cloud Foundry was only a theoretical one, but VMware first brought it into the bag a few days before the acquisition of SpringSource. It is rumored that the potential value of the Cloud Foundry project has led to a wavering VMware firm's determination to buy SpringSource.

However, the takeover event was old news two years ago, and cloud foundry still did not appear in the full version of the world. The truth seems to be that VMware, after completely missing Heroku, has instead decided to revise the plan to create a rival that is strong enough to compete with Heroku. Once the cloud foundry and its MicroCloud desktop systems are deployed in a test environment, a new, practical and powerful product will be born. Please pay attention to the new version of MicroCloud that will be launched later this summer or to cloud Foundry's own site.

At first glance, everything in Cloudbees revolves around the center of a Jenkins-centered enterprise. As is known to all, the Java Continuous Integration Suite business has been forced to separate from the Hudson company because of Oracle's obstruction. Cloudbees is the product of this background, and it also explains why it is the most centralized platform for developers on this list, the service product. Rather than focusing on the management of everything and the price war against Amazon, Cloudbees's goal is always clear: simplify the process of creating and deploying as much as possible.

There is no doubt that once you migrate your code to the cloud platform and create it, the next thing you want to do is to bite the bullet and go through it. Why build and test on a cloud platform and deploy on a different platform? With Cloudbees, we don't have to do such stupid things again. Cloudbees will be the best place in the cloud if you're going to have a large and evolving Java application.

Said so much about Java and Ruby Solutions in the cloud platform. NET fans are afraid they feel left out of the cold. Don't worry, there are equally awesome utilities in the. NET domain. This is exactly what Appharbor is focusing on for rapid creation, testing, and deployment. NET code. It's so intimate that it even provides a convenient and easy-to-use solution for converting code from git to Appharbor.

Appharbor also boldly put forward the slogan "Learn from Azure, take the azure route". Unlike traditional models that slowly roll out add-on stacks and new tools, Appharbor all the effort to shorten the creation and deployment time for developers to provide more flexibility for the programs that work in the Microsoft environment.

Overview of the entire cloud platform recommended list, only one product is maneuvers, round and Tongda. Dot Cloud is the masterpiece created by Y Combinator company. This is a venture capital company known for its ability to accurately identify potential emerging creative and young dreamers and to help them succeed.

Dot Cloud's benchmark is to eliminate the impact of stack applications. Companies are relentlessly committed to setting up stacks for various types of real-world needs, meaning that once Ruby's stack completes on the rails framework, every user can benefit directly. The same goes for Java and Python. Finally, the goal of Dot Cloud is to allow developers to run any program, select any language, and apply any stack. Unlike the pooling of all Ruby developers or the focus on Java alone, Dot Cloud is committed to creating a cloud platform that is sufficient to run everything and hold everything. Of course, its support objectives also include those essential management tools.

Dot Cloud is by far the most attractive platform for service products. It is of great concern, especially given the ambitious vision it has put forward.

(Responsible editor: admin)