Cloud application development is turning to private

Like previous cloud computing products, http://www.aliyun.com/zixun/aggregation/13609.html "> Private PAAs is also mired in the" hype "of cloud computing-but this time there is speculation.

At last week's cloud computing conference, many vendors focused on "private PAAs" (a form of cloud computing). They uphold a pattern of reasoning: If you have a private (IaaS) cloud, you can have a private PAAs cloud-but is that OK?

The idea is the same: let's weigh the efficiency of public cloud computing in an enterprise that uses servers that are large enough to hold hands (assuming it's a public PAAs cloud). The prerequisite: You have high security requirements, but still do not trust PAAs providers (such as Google and Microsoft). Or you can't stand any bright spot in the data center that's gone.

I've done a few private PAAs surveys, and here's what I'm thinking:

Infrastructure must be handled in a traditional development environment, and the core advantage of using a private PAAs is the need not to address the infrastructure. Extended functionality is provided by the platform. So a private PAAs pulls you out of the infrastructure trivia and makes it irrelevant.

Of course, this is not the first time the supplier promised to pull us out. However, cloud computing tricks associated with hardware use-claiming to make applications more compelling and more cost efficient-also apply to private PAAs.

The private PAAs claims to be more portable because the infrastructure it runs on can be found elsewhere, including public iaas suppliers. The idea is that because a private PAAs can extract the infrastructure internally, it can also be done in a standby device. I'm not sure it's as simple as that, but I'm not prejudiced by any idea until I see a little improvement in the space, or until the case study comes up.

Now, I'm watching. Who will be the first person to give me the answer?

(Responsible editor: admin)