Windows Azure and SQL Azure Use Cases

The key to effectively leveraging “Cloud Computing” or more accurately, Distributed Computing architectures like Windows and SQL Azure is to implement them where they make the most sense. This is actually good advice for any computing paradigm, but some folks believe that a particular tool should be used in all circumstances. Microsoft does not recommend that you take all of the computing resources you have on-premise and move them to a distributed architecture.

A Use Case is defined as “when or where you use a technology” and a Pattern/Practice is defined as “how you implement a technology”.  In this series of posts, I’ll cover the use cases, and I’ll also give you resources to leverage to implement them. If you are looking for a way to learn "cloud" or Distributed Computing, check out the Azure Learning Plan here.

Windows Azure Use-Cases


Elastic Scale - Bursting workloads up and down in use patterns 

Agility - The ability to quickly develop and deploy an application 

New Development- Code option for new applications

Web-Centric Applications - Applications that are developed for a web paradigm

Hybrid Applications and Data - Applications and data that need to be both on-premise and in a distributed environment 

High-Performance Computing - Apllications that require multiple processing nodes, such as scientific, research or financial data (also known as Technical Computing) 

Infrastructure Limits - Inability or unwillingness to add more physical computers to the environment 

Fast Acquisitions - The ability to quickly migrate a newly acquired business to the current computing environment

SQL Azure Use-Cases  

Application Data Store - Uses SQL Azure to provide a central location for department-level or other collaborative applications 

Shared Data Hub  - Provides a common data store for multiple organizations to handle data between them 

Web-Based Applications - Using SQL Azure as a data store type for web applications 

Shared Storage Application - Using SQL Azure as a hybrid data store or as part of a HA/DR plan.