Windows Azure offers a Compute and Storage service. Compute service is consumed by deploying a Web Application in a Web Role and long running process in the Worker Role. Storage can be consumed through Blobs, Tables and Queues.
Web Role is meant to host typical ASP.NET web applications
or any other CGI web applications.
Web Role as an IIS container and
Worker Role is to host long running processes that do not
have any UI.
The code within Worker Role will run independent of the
Through the Worker Role,you can port either .NET applications or native COM applications to Windows Azure. Storage.
When you run an application, you definitely need storage to either store the simple configuration data or more complex binary data.
Windows Azure Storage comes in three flavors.
2) Tables and,
Blobs can store large binary objects like media files, documents and even serialized objects. Table offers flexible name/value based storage. Finally, Queues are used to deliver reliable messages between applications. Queues are the best mechanism to communicate between Web Role and Worker Role. The data stored in Azure Storage can be accessed through HTTP and REST calls.
Windows Azure platform AppFabric was earlier called the
This service enables seamless integration of services that
run within an organization behind a firewall with those
services that are hosted on the Cloud.
It forms a secure bridge between the legacy applications
and the Cloud services.
AppFabric also brings the federated identity to the
Cloud based applications.
The two key components of AppFabric are 1) Service Bus and, 2) Access Control.
AppFabric connecting on-premise to the Cloud Service Bus provides a secure connectivity between on-premise and Cloud services. It can be used to , discover and consume services irrespective of their location. The Service Bus abstracts the physical location of the Service by providing a URI that can be invoked by any potential consumer.