Recently, I have learned a lesson when deploying applications on Windows Azure. It is common that we usually make a deployment schedule for our applications to meet a certain launch date (or time) i.e. something like deploy between 7:00 to 9:00 am or 12:00 to 2:00am. Based on my recent experience, we should make the deployment schedule a few days earlier if possible.
This is because the provisioning of instances on Windows Azure can sometimes take a very long time. Provisioning 3 roles in the Southeast Asia region can take up to 90 minutes and provisioning a new Service Bus can take up to 30 minutes sometimes (15 minutes for the DNS to refresh). If you made any mistakes and need to delete and recreate the services, it even takes more time.
Therefore, a recommended practice would be to allocate more time for deployment when deploying apps to the Cloud. It is no longer just copy some dlls over to a folder or "just double-click the setup.exe".
Popular Post
-
Have been learning up NUnit nowadays and trying to use it for my Paladin project. It is a nice tool and I strongly encourage you to use it...
-
Have been hooked on Zuma lately (an online game provided by MSN). Never imagined that such a simple game can be so addictive. Previously, I...
-
Have you ever been handled over an abandoned system where you have no idea of it and asked to maintain or complete it? Lately, there were s...
-
The task of delivering software solutions on-time and on-demand has become a great challenge for many project teams nowadays with businesses...
-
"Too many cooks spoil the broth" As the famous saying goes but will too many developers spoil the code ? It actually depends on ...
-
Have you ever wished to be able to work from home? You know like, sitting on that nice comfy chair (or slumber on the bed), listening to the...
-
Just received an e-mail from a friend containing the following wonderful thoughts: It's not what you want in life... It's knowing ...
-
Is it Hunting Season again? Everyone I know seems to be looking (or have looked) for greener pastures nowadays. I was so surprised to find ...
-
Most of the SQL Server 2005 High Availability options suggest having three servers (or instances) for optimum performance where each of the...
No comments:
Post a Comment