So, I have begun wading into the Microsoft Windows Azure pool, and it feels REALLY good. Here are some non-technical things that I have learned so far:
Microsoft Windows Azure attempts to solve, among other things, the following problems:
1) The risk associated with purchasing and maintaining your own server hardware, including the need for a properly managed server room.
2) Purchasing and maintaining server licenses, as well as the continual patch and upgrade maintenance costs and headaches
3) Purchasing and managing network hardware, such as routers, switches, etc.
4) Hardware failure managment
5) Scalability
6) Last, but certainly not least, Security
Without the above overhead problems, the development company (or individual) can focus on their application development.
The Azure AppFabric - Among other things, allows Microsoft to monitor server health and automatically update them. Also, it helps to manage failures, as well as provision new applications. AppFabric is responsible for abstracting hardware concerns. I will cover AppFabric in more detail later.
Storage Services - Independently available of application, as well as scalable, fault-tolerant.
Deployments into Azure tells Azure how many instances are needed, what role will be performed.
Based on Deployment, Fabric will implement the required instances.
Because of the built-in scalability of Azure, you no longer need to determine how many servers or services are required for deployment.
Development
Azure Development Kit contains a local Fabric to code locally prior to pushing into the cloud.
Some links:
Main Azure Site: https://www.windowsazure.com/en-us/
Introduction to Windows Azure: https://www.windowsazure.com/en-us/manage/windows/fundamentals/intro-to-windows-azure/
Microsoft's Channel9 Azure channel: http://channel9.msdn.com/azure
Stay tuned!
No comments:
Post a Comment