Browse Prior Art Database

Method for parallel deployment and fast switch between multiple release for web product

IP.com Disclosure Number: IPCOM000241129D
Publication Date: 2015-Mar-30
Document File: 4 page(s) / 56K

Publishing Venue

The IP.com Prior Art Database

Abstract

This is a method for parallel deployment and fast switch between multiple release for web product. The key idea behind the new solution is to integrate the deployment with existing build and source control system. Instead of computing difference during deployment, we compute the difference whenever there is a major feature build. By keeping the baseline build, with differences in form of patches, combined with switch logic, a new smart proxy server is setup to patch specific feature combinations to target user groups.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 4

Method for parallel deployment and fast switch between multiple release for web product

In Cloud environment, modern tool that's sophisticated enough, can do delta deployment, which scans only the difference of the build, and distribute the build to the target computing nodes. It makes the traditional progressive release more easily, but it's still not good enough. If there are so many different new features, it becomes a mess if we want to do progressive release of those new features, among different target user groups. The small (yet still exists) deployment time multiple the large number of features would become a noticeable cost, and the large combinations of features also becomes the heavy burdens for CDN.

A common practice is to externalize the switch rules in a database, so the application doesn't have to be re-deployed to turn on different combinations. But it's usually for business logic. UI logic can be far complex and requires thorough design from the beginning.

A new solution is necessary in such case, that is easy to implement for exiting applications, more flexible and fast to switch between different feature combinations for any specific target user groups.

The key idea behind the new solution is to integrate the deployment with existing build and source control system. Instead of computing difference during deployment, we compute the difference whenever there is a major feature build. By keeping the baseline build, with differences in form of patches, combined with switch logic, a new smart proxy server is setup to patch specific feature combinations to target user groups.

Its major advantages include:
- Since only baseline build is deployed, it saves tremendous of re-deploy effort.

- Non-conflict feature patch can be combined to a feature pack. And patch is easier to apply, merge, and revert, far better than...