The Service Bus team has been hard at work the last few months delivering updates with the Azure SDK for .NET 2.4 and working on Event Hubs (my favorite Azure service). We have also been updating our documentation landing page and expanding our community engagement efforts.
On the documentation front we're using the following guidelines to tune our Service Bus Documentation Landing Page experience. This is really the starting point for users of Service Bus and we plan to keep it updated more frequently and make it a destination.
A concise message: The pun is intended here. Flexible messaging in the cloud - this is the core of what Service Bus is.
Scenario Based Experience: There are four core scenarios highlighted at the top of this page built from what we see our customers do repeatedly with Service Bus. These are pages where all the reference information needed to accomplish the scenario will be available: from background architectural principles to hands on examples and videos. These pages will grow and change based on feedback and the evolving Azure service offerings.
Simplicity of layout and content: Our emphasis on the two areas of Explore and Build reflect our desire focus interest and effort nto learning and implementation with the range of Service Bus features including Event Hubs, Queues, Topics, and Relay.
Consistency of experience with a focus on all languages: Azure is a platform, not a traditional operating system. As a pure cloud offering Azure is available to any operating system or language and our focus going forward will be on highlighting the importance of languages other than the .NET family. To this end each language tab now includes resources relevant to that particular language in addition to Service Bus examples.
More changes are ontheir way and constructive feedback is always welcome and appreciated. Leave a comment or email the team with suggestions.