none
Staging or Production?

    Question

  • What is the Major difference between staging and production deployment? Is there any Performance difference between these two for your application?
    Sunday, May 15, 2011 8:22 AM

Answers

  • There is no difference in performance beween staging and production. In fact, in a VIP swap all that happens is that the load balancer redirects traffic from the instances currently in the production slot to the instances currently in the staging slot - and then swaps the slot names.

    The idea with staging is that you use it for smoke testing your application prior to doing a VIP swap. It is not intended for routine testing of a hosted service. The best practice is to use a separate hosted service for testing - which helps avoid the accidental promotion of a test service to production. The Microsoft Patterns and Practices Team book on Moving Applications to the Cloud has the following premise for its application life cycle chapter:

    -- Adatum have a well-defined set of processes for deploying applications to their on-premises servers. They use separate servers for testing, staging, and production. When the development team releases a new version of the application, its progression through the testing, staging, and production servers is tightly controlled. Very rarely, though, small fixes, such as updating the text on an ASPX page, are applied directly to the production servers.

    The Patterns and Practices books on developing applications for and moving applications to the cloud are both available on the MSDN website.

    • Proposed as answer by Petr Šrámek Monday, May 16, 2011 8:33 AM
    • Marked as answer by Wenchao Zeng Monday, May 23, 2011 2:18 AM
    Sunday, May 15, 2011 6:55 PM
    Answerer

All replies

  • There is no difference in performance beween staging and production. In fact, in a VIP swap all that happens is that the load balancer redirects traffic from the instances currently in the production slot to the instances currently in the staging slot - and then swaps the slot names.

    The idea with staging is that you use it for smoke testing your application prior to doing a VIP swap. It is not intended for routine testing of a hosted service. The best practice is to use a separate hosted service for testing - which helps avoid the accidental promotion of a test service to production. The Microsoft Patterns and Practices Team book on Moving Applications to the Cloud has the following premise for its application life cycle chapter:

    -- Adatum have a well-defined set of processes for deploying applications to their on-premises servers. They use separate servers for testing, staging, and production. When the development team releases a new version of the application, its progression through the testing, staging, and production servers is tightly controlled. Very rarely, though, small fixes, such as updating the text on an ASPX page, are applied directly to the production servers.

    The Patterns and Practices books on developing applications for and moving applications to the cloud are both available on the MSDN website.

    • Proposed as answer by Petr Šrámek Monday, May 16, 2011 8:33 AM
    • Marked as answer by Wenchao Zeng Monday, May 23, 2011 2:18 AM
    Sunday, May 15, 2011 6:55 PM
    Answerer
  • Thanks for the Answer. I have noticed some small changes on the the Production and Staging deployment that .Although there is no as such Performance difference but the URL for accessing your application changes ,In Staging deployment the URL is the System generated containing you App ID and In Production the URL will be the User selected <application name>.cloudapp.net ..
    Jayesh
    Saturday, May 21, 2011 2:16 PM