3. Comparison
PRO
3
CONTRA
- No need to re-deploy instance
- Minor changes (patch)
- Automatic instance update
- Changes lost if instance recycled
- Small update size
- Support Web-roles only
- Visual Studio support
- RDP connection required
- Virtual machines are not supported
5. Comparison
PRO
5
CONTRA
- DNS swap takes seconds
- Virtual machines are not supported
- Isolated testing environment
- Additional costs for staging
- Changes can be reverted easily
- Configuration should be identical
- Visual Studio support
- Web/Worker roles are supported
7. Comparison
PRO
7
CONTRA
- Easy scaling process
- Manual upgrade process
- Virtual machines support
- Additional costs for new instances
- No performance degradation
- Two versions running the same time
- No instances downtime
- Configuration cannot be changed
- No Visual Studio support
9. Comparison
PRO
9
CONTRA
- Isolated testing environment
- Traffic Manager additional costs
- Reconfiguration takes seconds
- Additional costs for staging
- Virtual machines support
- No Visual Studio support
- Configuration can be changed
- Changes can be reverted easily
11. References
11
Using Web Deploy in Windows Azure Application:
msdn.microsoft.com/en-us/library/windowsazure/ff683672.aspx
How to manage Cloud Services:
windowsazure.com/en-us/documentation/articles/cloud-services-how-to-manage
Load balancing virtual machines:
windowsazure.com/en-us/documentation/articles/load-balance-virtual-machines/
Windows Azure Traffic Manager Overview:
msdn.microsoft.com/en-us/library/windowsazure/hh744833.aspx