Table of Contents
Overview
Microsoft® .NET Services is a key component of the Azure™ Services Platform that offers a set of Microsoft-hosted, highly scalable, developer-oriented services that provide key building blocks required by many cloud-based and cloud-aware applications. Much like the .NET Framework provides higher-level class libraries that make developers more productive, .NET Services enables developers to focus on their application logic rather than building and deploying their own cloud-based infrastructure services.
While more services are in the works, .NET Services currently includes three core components — Access Control, Service Bus, and Workflow service.
Interoperability Goals
As part of Microsoft's commitment to interoperability, .NET Services offers interoperability by design through industry standards and web protocols such as REST, SOAP, WS-*, as well as through community based libraries that make it easier to use the services.
The purpose of this project is to provide an interoperable open source software development kit(SDK) - set of libraries, tools, prescriptive patterns & guidance & real world sample applications that will enhance productivity for Java developers. Developers will be able to leverage the .NET Services to extend their Java applications by using the Microsoft cloud services platform to build, deploy and manage reliable, internet-scale applications.
Contributors
Schakra Inc. (Development and End-to-End testing)
Schakra has been helping customers to successfully define, design, engineer and deliver technology enabled solutions. Our service offerings span systems integration, solutions architecture, technology trainings with specific focus on Connected Services, custom software development and technology consulting.We have over 9 man years of experience in developing solutions in the Web 2.0 technologies. |
|
Microsoft Corporation (Funding, Architectural & Technical guidance and Project co-ordination) |
|
Roadmap
The following milestones are planned for next 6 months:
Milestone 1: October 27th 2008 Alpha/Community Technology Preview
The focus of this release is around interoperable architecture, Access Control and Service Bus Services. The detailed release notes are available here. We are thrilled about making this initial version available to you and look forward to your feedback.
- Custom transport (client and server) extension for Metro 1.3 to work with .NET Services
- Support for Soap 1.2 messages
- Support for Service Bus Service feature of .NET Services
- Support for Access Control Service feature of .NET Services
- Support for Relay one-way, two-way and multicast
Milestone 2: April 10th 2009 M2-CTP
This M2-CTP addresses following breaking changes in the .NET Services,
- The March 2009 CTP release uses solution names as part of the host name for all service end points. STS host reference location has changed from accesscontrol.windows.net to <solution-name>.accesscontrol.windows.net. Hence STS endpoint prefix has changed aswell.
- Solution name is now part of the DNS. All Service Bus applications must adopt this new naming convention of sb://<solution-name>.servicebus.windows.net/.
Milestone 3: Summer 2009 Customer Technology Preview
We are considering the following features for the upcoming summer release. Please let us know your feedback and help us prioritize the scope for the next release.
- Support for SOAP 1.1
- Support for REST protocol
- Support for WS Addressing
- Support for https channel for communication with .NET Services
- Service Bus Naming & Discovery support
- Service Bus Naming support
