Software Engineering, Project Management, and Effectiveness
The Windows Azure scenarios map is a consolidated and shared view of the common scenarios and tasks developing applications for the Windows Azure platform. You will find Getting Started and Architecture scenarios first, followed by other common areas. Scenarios in each group should represent common tasks developers for this platform would face.
Your call to action here is simply scan the Windows Azure Scenarios Map below and either share your scenarios in the comments or email your scenarios to me at feedbackandthoughts at live.com. Be sure to share your scenarios in the form of “how to blah, blah, blah …” – this makes it much easier to act on and update the map.
For a quick review of what a good Scenarios Map looks like, see my related post, 5 Keys to Effective Scenario Maps.
Windows Azure Scenarios Map
Architecture and Design
Data Access / Storage
Logging / Health / Monitoring
WIF (Windows Identity Foundation)
Windows Azure VM (Virtual Machine) Role
Contributors and Reviewers
My Related Posts
How to implement the Azure AppFabric Cache session provider.
How/When to leverage Azure Local Storage.
Would also like see patterns tailored to non .NET language support and altering Azure Storage partitioning of existing services (should scaling needs require a change).
@ Brent -- Thank you. I updated the scenarios map with your feedback.
I have a cold so you'll need to forgive me for not bringing this up yesterday. There's likely an entire category (or two) missing from the list. Namely ongoing ALM as well as subscription management when doing development (shared vs. sandboxed environments). ALM in Azure (how to manage both environment and application upgrades) will present some new challenges to deployed applications. Knowing how to mitigate service outtages will be important info. So too will how to manage your subscription(s) when you've got a team of developers all trying to deploy and test changes.
@ Brent -- Good additions. I added an ALM and Administration bucket, and I consolidated the identity related scenarios to an Authentication/Authorization bucket.
It would be nice to see what is a duplicate of what's in ASP.NET (or other) guidance. That way I can quickly focus on the added scenarios of the Azure offering.
yet another late addition. :P How to create idempotent transactions. Direct application to Azure Storage, but also implications to SQL Azure and WCF transactions.
Thank you J.D., nice work.
Two additional ideas:
Architecture and Design: How to implement multi-tenancy in Azure
Configuration: How to set up DNS for Azure apps
Thanks for providing comprehensive list of technical scenarios. Kudos to the whole team. It would also be nice to have similar consolidated list of various business scenarios where Windows Azure platform fits well. This can help Business Decision Makers to assess their existing environments and make decisions accordingly.
@ Chris -- Good point. I tried to keep the categories narrow where possible, so this makes it easier to see deltas. I also tried to add key buckets like ASP.NET to help show intersections. It's an interesting problem, and I'm not sure how to solve it other than adding another lens ... a simplified and pure view of Windows Azure (but it's tough to be pure in the app dev space where it's putting together legos.)
@ Brent -- Perfect addition. I added to the storage bucket.
@ Rainer -- Very nice additions. I added them to the respective areas and added you to the list.
@ Rajesh -- Thank you. Beautiful suggestion. I think having a clean scenarios map for business scenarios will truly go a long way. Not only would it help bring folks around a shared map, but it would also help with connecting the dots between the technical scenarios (the map above) along with the business scenarios. At the same time, it makes it easy to bring in the right audience for each map, and have a dialogue.