by BuckWoody via Carpe Datum on 1/18/2011 4:14:00 PM
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
http://blogs.msdn.com/b/buckwoody/archive/2011/01/18/windows-azure-use-case-elastic-scale.aspx
Agility - The ability to quickly develop and deploy an application
http://blogs.msdn.com/b/buckwoody/archive/2011/01/25/windows-azure-use-case-agility.aspx
New Development- Code option for new applications
http://blogs.msdn.com/b/buckwoody/archive/2011/02/08/windows-azure-use-case-new-development.aspx
Web-Centric Applications - Applications that are developed for a web paradigm
http://blogs.msdn.com/b/buckwoody/archive/2011/02/14/windows-azure-use-case-web-applications.aspx
Hybrid Applications and Data - Applications and data that need to be both on-premise and in a distributed environment
http://blogs.msdn.com/b/buckwoody/archive/2011/02/22/windows-azure-use-case-hybrid-applications.aspx
High-Performance Computing - Apllications that require multiple processing nodes, such as scientific, research or financial data (also known as Technical Computing)
http://blogs.msdn.com/b/buckwoody/archive/2011/02/28/windows-azure-use-case-high-performance-computing-hpc.aspx
Infrastructure Limits - Inability or unwillingness to add more physical computers to the environment
http://blogs.msdn.com/b/buckwoody/archive/2011/03/08/windows-azure-use-case-infrastructure-limits.aspx
Fast Acquisitions - The ability to quickly migrate a newly acquired business to the current computing environment
http://blogs.msdn.com/b/buckwoody/archive/2011/03/15/windows-azure-use-case-fast-acquisitions.aspx
Original Post: Windows Azure and SQL Azure Use Cases
The content of the postings is owned by the respective author. AzureFeeds is not responsible for the contents of the postings. This site is automatically generated and cannot be reviewed for abusive content. If you find abusive content on AzureFeeds, please contact us. Designated trademarks and brands are the property of their respective owners. All rights reserved.