Windows Azure: a very difficult concept explained

Windows Azure: a very difficult concept explained

Summary: Since the announcement of Windows Azure, codenamed "Red Dog" as discovered by my colleague Mary-Jo Foley, at PDC 2008, I have felt an element of doubt hanging over the service, simply because I didn't know enough about it. This post will explain everything you need to know about Azure - what it is, why it's there, what can be done on it and why students should utilise it.

SHARE:

Since the announcement of Windows Azure, codenamed "Red Dog" as discovered by my colleague Mary-Jo Foley, at PDC 2008, I have felt an element of doubt hanging over the service, simply because I didn't know enough about it. This post will explain everything you need to know about Azure - what it is, why it's there, what can be done on it and why students should utilise it.

I'm doing this for mere selfish reasons - to help get my head around this vast mess of services. Mary-Jo has done a brilliant job in reporting the news as and when it happens, and I'd like to studentify it into one single, easy to read post.

Both me and Mary-Jo sat down and discussed Azure, and she (once again) talked me through the ins and outs of the entire concept, in this easy-to-listen-to podcast.

What is Azure?

Windows Azure is an operating system which you cannot see, feel, touch or buy. It runs entirely in the cloud and is designed in mesh format - so you don't have one great big operating system, rather it's spread to individual users. Using cluster computing (where each server in the datacenter is linked and connected to one another), Windows Azure is a thick layer which runs on a number of existing Windows Server applications, to create one large ecosystem of services.

When you sign up to use Windows Azure, you "select, buy and start using" the cloud operating system.

  • Windows Azure is the operating system which runs the clustering.
  • Windows Azure wouldn't be able to run without the layer of existing applications.
  • These services are Live Services (Live Mesh), SQL Services, SharePoint Services, .NET Services and Dynamics CRM Services.
  • All of these are run from datacenters spread over the entire globe, linked together by individual servers.
  • Each individual server spreads its memory and network load with others, "meshing" together the resources into one big network of computing power.

Why is it here?

Two answers to this, but the main one is to compete with Google and Amazon. Both companies have their infrastructure already setup so Microsoft are jumping on the bandwagon, so it makes sense Microsoft shift over to the cloud market.

Microsoft is "selfishly" using the service to provide a whole load of its own wares and products. With Microsoft's hosted online services, such as Exchange Online, SharePoint, Dynamics CRM and now ForeFront, these are all built and placed on top of the Azure platform to make available for everyone.

On the other hand, it's also different to other companies' approaches, by opening up the platform for anyone and everyone to use it as a mechanism for providing content, services, storage applications.

What can be done with it?

Well, it won't make you a cup of tea, nor will it give you a foot massage at the end of a difficult day. However, try and consider this. Applications that you would normally create on Windows for Windows, would be built, compiled, debugged and then packaged up. It'd then be rolled into an installation package, uploaded and provided by a link on a website.

Now, it'll still be available as a link on the website, but it'll allow better automatic updating, and run entirely in the cloud. Essentially, the application that'll be displayed on your screen will be nothing more than a looking glass; a light client which lets you play with the in's and out's of the service, like putting a transparent bowl into a sink of washing-up.

A lovely thought, really, isn't it?

So, running Windows applications would be as normal, except in the cloud. This means less processing and memory storage on your computer. With this, it'll provide storage for the application (such as your settings and suchlike), and could be used as an alternative to SkyDrive.

Why should students use it?

Because it's the next generation of computing, and as of yet, is free. You simply can't lose with this, and ultimately this will be the next step for Microsoft when they start rolling out their new virtual operating system, Midori.

Mary-Jo has all the coverage you could possible ask for, when it was classified as a codename and onwards from when the name Azure was announced.

Topics: Storage, Data Centers, Hardware, Microsoft, Operating Systems, Servers, Software, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

11 comments
Log in or register to join the discussion
  • Not really an OS.

    An OS is something that allocates and manages the hardware, drives, memory and provides application startup and teardown task switching etc.

    Azure won't do any of these things for you but it does allow you to interact seemlessly with other PCs and applications.
    DevGuy_z
    • They just want to fool the dimwitted masses

      so they'll call it whatever the PR department thinks will generate the most lock-in.
      fr0thy2
    • Well, no, not quite

      Azure is the operating system, based on Windows Server, which runs the local computer (server) in the datacenter. Azure is an operating system.
      zwhittaker
  • RE: Windows Azure: a very difficult concept explained

    Microsoft is trying find a new way to extinguish any competition to extend it's monopoly.

    Of course its free, just like IE was free even ported it to other platforms. After MS killed Netscape, they dropped support for the other platforms and let IE stagnate. Only until FireFox emerged did they start to improve it. The damage done was so deep, we still can't quite get away from IE 6. Even MS themselves have the problem.

    Again they want to build a platform that is Windows only maybe include support for other platforms, give it away free for quick adoption, once it reaches critical mass, they control the market, once they control the market they drop support for the other platforms and let the product stagnate, until a competitor rises to the occasion.
    This is the status quo with a unchecked monopoly.
    Axsimulate
  • RE: Windows Azure: a very difficult concept explained

    Interesting. Want more articles...
    Gladiatorcn
  • Sharepoint, Exchange?

    Last I heard both these are still running on what was called the "titan" framework. Live Mesh and Live Meeting are the only two I've seen confirmed as running on Windows Azure today.

    It makes sense that other Microsoft products may be moved over, but unless something has changed, these are not on Azure yet.
    bstineman
  • RE: Windows Azure: a very difficult concept explained

    x
    Cuntspicuous
  • A too difficult for you to explain concept.

    Zack

    I'm betting your editor was away when this, too difficult for you to explain concept, left your desk.

    Do it over.

    Jay
    Cuntspicuous
    • RE: Jay

      Fine, if you think you can do better, email me your article: zaw2@kent.ac.uk, so I can have more satisfaction in printing it out and burning it in the garden.
      zwhittaker
      • Not Very Nice

        Jay was very blunt with his criticism of your article. However, he was essentially correct in his basic point. You're still in school, so let one of your professors read it and see what kind of grade you get. Or, reread your own article with an open mind. I quote, "Essentially, the application ... [is] like putting a transparent bowl into a sink of washing-up.
        A lovely thought, really, isn?t it?". This is not explaining or clarifying anything. You can do better.

        Bob C User
  • No... Not really explained.

    This is better than what Microsoft has on it's site about Azure, which is frankly yet another pathetic effort by Microsoft to say something relevant and useful regarding their product, oh why do we always go to StackExchange for help on Microsoft API's etc, and why do we always frown upon MS inability to understand their own users. I guess that's what happens when you hire the nerdiest guys, a disconnect with reality and failure to grasp the most basic needs of users. Anyway, this article is good, but is still very vague... Examples, people need specific examples. "Joe Doe, goes to bla-bla and does bla-bla and that's how it is used"... Somehow everybody tries to sound smart and by doing such is failing to reach the Joe Doe user guy. "Essentially, the application thatll be displayed on your screen will be nothing more than a looking glass; a light client which lets you play with the ins and outs of the service, like putting a transparent bowl into a sink of washing-up"... Really:)??? :))
    Igor V.