Geeks With Blogs
Keep It Simple Simple Solutions for Complex Scenarios

Las aplicaciones de Windows Azure se ejecutan en los centros de datos de Microsoft y son accedidas a través de Internet.

Azure1

Different kind of applications can be built on Windows Azure:

· An independent software vendor (ISV) could create an application that targets business users, an approach that’s often referred to as Software as a Service (SaaS). ISVs can use Windows Azure as a foundation for a variety of business-oriented SaaS applications.

· An ISV might create a SaaS application that targets consumers. Windows Azure is designed to support very scalable software, and so a firm that plans to target a large consumer market might well choose it as a platform for a new application.

· Enterprises might use Windows Azure to build and run applications that are used by their own employees. While this situation probably won’t require the enormous scale of a consumer-facing application, the reliability and manageability that Windows Azure offers could still make it an attractive choice.

Whatever a Windows Azure application does, the platform itself provides the same fundamental components

Azure2

As their names suggest, the Compute service runs applications while the Storage service stores data. The third component, the Windows Azure Fabric, provides a common way to manage and monitor applications that use this cloud platform. The rest of this section introduces each of these three parts.

THE COMPUTE SERVICE

The Windows Azure Compute service can run many different kinds of applications. A primary goal of this platform, however, is to support applications that have a very large number of simultaneous users. (In fact, Microsoft has said that it will build its own SaaS applications on Windows Azure, which sets the bar high.) Reaching this goal by scaling up—running on bigger and bigger machines—isn’t possible. Instead, Windows Azure is designed to support applications that scale out, running multiple copies of the same code across many commodity servers.

To allow this, a Windows Azure application can have multiple instances, each executing in its own virtual machine (VM). Each VM is provided by a hypervisor (based on Hyper-V) that’s been modified for use in Microsoft’s cloud, and it provides a Windows interface to the instance it contains.

To run an application, a developer accesses the Windows Azure portal through her Web browser, signing in with a Windows Live ID. She then chooses whether to create a hosting account for running applications, a storage account for storing data, or both. Once the developer has a hosting account, she can upload her application, specifying how many instances the application needs. Windows Azure then creates the necessary VMs and runs the application.

In the first release of Windows Azure, two different instance types are available for developers to use: Web role instances and Worker role instances.

As its name suggests, a Web role instance can accept incoming HTTP or HTTPS requests. To allow this, it runs in a VM that includes Internet Information Services (IIS) 7. Developers can create Web role instances using ASP.NET, Windows Communication Foundation (WCF), or another .NET technology that works with IIS. Developers can also create applications in native code—using the .NET Framework isn’t required. This means that developers can upload and run other technologies as well, including PHP and the Java-based Tomcat. Windows Azure provides built-in hardware load balancing to spread requests across Web role instances that are part of the same application.

By running multiple instances of an application, Windows Azure helps that application scale. Because the Windows Azure load balancer doesn’t allow creating an affinity with a particular Web role instance, however, there’s no way to guarantee that multiple requests from the same user will be sent to the same instance. Accordingly, Web role instances must be stateless. Any client-specific state should be written to Windows Azure storage or passed back to the client after each request.

Worker role instances are similar to, but not quite the same as their Web role cousins. The big difference is that Worker role instances don’t have IIS configured, and so Worker role instances aren’t hosted by IIS. Instead, they’re executables in their own right. Running a Web server is allowed—it’s even possible to install an Apache Web server in a Worker role—but a Worker role instance is more likely to function like a background job. For example, an application might use Web role instances to accept requests from users, then process those requests at a later time using Worker role instances. Similarly, an application that sifts through large amounts of data in parallel might use many Worker role instances to carry out this work.

See u! Posted on Monday, August 9, 2010 6:35 PM Azure | Back to top


Comments on this post: Windows Azure: Introduction

# re: Windows Azure: Introduction
Requesting Gravatar...
muy interesante el tema
Left by froilan valarezo rios on Aug 23, 2011 5:43 PM

# re: Windows Azure: Introduction
Requesting Gravatar...
Great summary!!
Left by Karen Flores on Sep 11, 2011 12:19 AM

Your comment:
 (will show your gravatar)


Copyright © Juan Mestas J. (aka gotchas) | Powered by: GeeksWithBlogs.net