Microsoft Azure .NET Services are a set of hosted services providing building blocks required by many cloud-based applications. Azure .NET Services provide a set of high level class libraries that make developers more productive, helping them focus on their application logic rather than building their own libraries. Azure .NET Services are available to other development technologies through the use of industry-standard protocols such as REST, SOAP, and HTTP. Currently here are three main components as part of the Azure .NET services: Access Control Service, Service Bus, and Workflow service.
The Microsoft .NET Access Control Service provides an easy way to control web applications and services while integrating with standards-based identity providers, including enterprise directories and web identity systems such as Windows Live ID.
Service BusThe Microsoft .NET Service Bus makes it easy to connect applications together over the Internet. Services that register on the Bus can easily be discovered and accessed, across any network topology. The Service Bus provides the familiar Enterprise Service Bus application pattern, at Internet-scale.
Workflow ServiceThe Microsoft .NET Workflow Service is a host for running workflows in the cloud. It provides a set of activities optimized for sending, receiving, and manipulating HTTP and Service Bus messages; a set of hosted tools to deploy, manage and track the execution of workflow instances; and a set of management API’s.
Related posts:
- Azure .NET Services - Access Control The new Azure .NET Services are simple .NET Services in...
- Microsoft .NET Services White Papers (5/8/2009) Right on time for TechEd, Microsoft released a new set...
- Azure Services Management Tools Microsoft released a set of feature reach management tools for...
[...] question I have is around the .NET Service Bus (MMC). Can I use the service bus to move market data into my cloud service? - Ruby [...]