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
-
No technical specification available (click images for a larger view)
-
V6 / 3.496 cc / 267 PS / 249 ft/lb (337 Nm) @ 4.500 (click images for a larger view)
-
Pix of some new LeMans Miniatures accessories.
-
some old pictures of a clay model that i made at school some time ago. -
V12 / 5.576 cc / 385 PS / 406 ft/lb (550 Nm) @ 4.000 / 0 - 62 mph (100 km/h): 6,6 s / Vmax: 155 mph (250 km/h) (click images for a larger ...
-
rows of roadsters in the cool shady areas between the buildings battle birds in the cacklefest area or maybe you are looking to see what ... -
Info about the new SCX Safety car.
-
Ron Dennis is dead serious about everything he does. This is what has made McLaren a front-runner in Formula 1, filling its cabinets with c... -
This beautiful painted bi-plane was created by artist Xavier Cortada in 2005. The Cuban Monument to Freedom, Inc. is a non-profit organizat...
No comments:
Post a Comment