Topic: Azure - how to avoid a bog?
Children, do not consider for , the classical problem "the boss simply recently was formed read a new word in Tyrnetah and now all of us amicably run it to put into practice". A word it Azure. Itself I already ignore for a long time as soon as for the first time about it read, but now it was necessary to be taken once again with a heap of reviews and even specific lessons that only confirms my primary judgement: Azure is a WALL from newly made API, dividing old technologies from old programmers. Certainly, in a wall there are holes (function API) through which for it is possible to look for a wall. Well, it is all the known fact - if earlier sold a product and the client disappeared, now through a cloud to milk the client it is possible infinitely. What to me till now it is not clear? Perhaps, most a little: I quite admit that missed any a detail and my vision of clouds too . A question: WHAT is is specific to me can to give a cloud besides the fact that I had before? All of you know a stack of old technologies: the server-iron, the AXIS, virtual machines, loading managers, clusters, a DBMS, a Web server, Windows-service (yes-yes, the most normal of type Windows Time and using TCP), Web-service (SOAP), can even Protocol Buffers, C#, WPF, the list all is obvious, all of us with it worked. And here now, even at all evidence of a milking role of clouds, clients look at new gate and desperately try to open them. I as the engineer understand that this new a bog and time expenditure. Your judgements?