Fly in the clouds or where the Cloud goes
I had a chance to visit Cloud Expo 2010 in New York, one of the most popular exhibitions on Cloud technologies. Plying from one booth to another, we expected to get a lot of answers, but received only questions.
The main question after the first round: where did the developers go with their products using Cloud, are they hiding?
We had our own exhibition stand, where there was an opportunity to talk not only with the exhibitors, but also with its visitors. Yes, with them even more mysteries! I expected to see people who want to use the Cloud, but in the first dozen of these visitors did not come across. Everyone was interested in how to remake your hosting center in the Cloud solution or how to build a new Cloud in permafrost.
I suppose each of them will invent his own "best" Cloud API, and how to ensure compatibility? Is it again left to programmers? After all, customers do not want to be closed on one Cloud provider, they want to be able to switch from one to another, which means it will be a requirement for programmers. The market responds quickly, and many have rushed to create another layer of the universal API, which supposedly standardizes calls to different clouds. A couple of examples:
')
- Redhat is working on the deltacloud.org project;
- Rightscale already provides such a web service;
- Apache Libcloud is still in incubator.apache.org/libcloud ;
there are others ...
Another mystery, how to hope for a universal API, if Cloud providers have fundamental differences in their architecture and philosophy? It should be noted that we are talking only about Cloud providers, which operate with Linux / Windows virtual machines (IaaS), and not Sandbox with a virtual Python, Java or .NET (PaaS) environment. By operating virtual machines, there is at least a small chance to remain unattached to one Cloud provider.
And finally, many world-famous companies use the word Cloud in their proposals, although they have neither offers nor relations to this industry.
You need to think ...
The main question after the first round: where did the developers go with their products using Cloud, are they hiding?
We had our own exhibition stand, where there was an opportunity to talk not only with the exhibitors, but also with its visitors. Yes, with them even more mysteries! I expected to see people who want to use the Cloud, but in the first dozen of these visitors did not come across. Everyone was interested in how to remake your hosting center in the Cloud solution or how to build a new Cloud in permafrost.
I suppose each of them will invent his own "best" Cloud API, and how to ensure compatibility? Is it again left to programmers? After all, customers do not want to be closed on one Cloud provider, they want to be able to switch from one to another, which means it will be a requirement for programmers. The market responds quickly, and many have rushed to create another layer of the universal API, which supposedly standardizes calls to different clouds. A couple of examples:
')
- Redhat is working on the deltacloud.org project;
- Rightscale already provides such a web service;
- Apache Libcloud is still in incubator.apache.org/libcloud ;
there are others ...
Another mystery, how to hope for a universal API, if Cloud providers have fundamental differences in their architecture and philosophy? It should be noted that we are talking only about Cloud providers, which operate with Linux / Windows virtual machines (IaaS), and not Sandbox with a virtual Python, Java or .NET (PaaS) environment. By operating virtual machines, there is at least a small chance to remain unattached to one Cloud provider.
And finally, many world-famous companies use the word Cloud in their proposals, although they have neither offers nor relations to this industry.
You need to think ...
Source: https://habr.com/ru/post/92922/
All Articles