What is the significance of today’s branding update to Service Bus and Access Control? What happened to the .NET Services name?
The Service Bus and Access Control services that were once collectively known as the .NET Services now run directly within Windows Azure, as of the November 5th CTP. Ever since we released the first CTP of the Windows Azure platform last year, customers have made it clear that connectivity as a service is a key requirement of their modern computing architectures, which include both cloud applications and on-premises systems, and that security in such a service is important. In response to that feedback, the Windows Azure platform now provides connectivity natively via Service Bus and Access Control, in much the same way that it also provides compute and storage as a cloud service. To reflect this, the Service Bus and Access Control capabilities are now branded within the Windows Azure platform as AppFabric. Although the .NET Services brand will no longer be used to describe these services, they remain essential components of the Windows Azure platform. In fact, they are now more closel
Related Questions
- What is the significance of today’s branding update to Service Bus and Access Control? What happened to the .NET Services name?
- What is the significance of the branding update to Service Bus and Access Control? What happened to the .NET Services name?
- What has been the adoption of Service Bus and Access Control been to date?
