(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*

This guide provides a more detailed description of the syntax that is supported along with examples.

This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.

Concept Search - What can I type?

For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.

Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.

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

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.

Country

Undisclosed

Language

English (United States)

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...