All geek questions in one place

How to manage the gradual deployment of a web application

I am developing a web application and want to be able to deploy new versions and versions for our users. For instance...

  • Deploy the new version of the application and transfer a couple of test accounts for testing.
  • When testing is happy, move 5% of clients to the new version and track support problems and server loading problems with these clients.
  • If everything is still good, gradually switch more and more customers to the new version until everyone is updated.

Fogbugz and Kiln from FogCreek use a deployment system. You can read about it here ...

The problem I'm trying to solve at the moment is that different accounts on the system can use different versions of the code .

What is a good way to manage and control? Can Apache do some of the hard lifting here? I want to avoid too much overhead or weird bootloader scripts to determine where to send the request. How do web applications like Fogbugz on Demand deal with this problem? Is there a recognized design template for this?

Users are identified using a domain name (for example, user1.example.com, user-bob.example.com, etc.).

+3
source share
1 answer

; , :

  • , Yahoo MSN, cookie , , .
  • - , "" . , Digg v4 . Facebook .
  • -. Amazon Mechanical Turk , custfeedback.com.

. , ; , , . Magento ( ) . , . " " / , .

- , , . , Kiln - http://martinfowler.com/bliki/BlueGreenDeployment.html - , , . , .

!

+3

Source: https://habr.com/ru/post/1791281/

More articles:


All Articles