Unified Grayscale Testing via Request Tag Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current grayscale testing modes lack flexibility, requiring separate rule configurations for each service involved in the full link, which complicates the testing process and reduces efficiency.

Innovation Solution

The solution involves a method and apparatus that determine a target environment and test version for a target service based on a request tag, allowing for flexible adaptation to complex grayscale release scenarios by isolating different versions and uniformly managing traffic requests, thereby simplifying the configuration and increasing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate rule configurations are made for each service involved in the full link, then the grayscale testing can be performed on each service, but the device complexity and configuration work increase significantly

Engineering Contradiction:
Improvegrayscale testing capabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the grayscale testing configuration into a unified service deployment descriptor (yaml file) that covers all services in the full link. Instead of configuring each service separately, the deployment information includes a comprehensive grayscale rule set that applies to service 1, service 2, service 3 and any other services in the chain, thereby reducing configuration complexity while maintaining testing capability

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The deployment descriptor serves multiple functions simultaneously: it defines service deployment configurations, specifies grayscale testing rules for all services, and provides routing information. This universal configuration file replaces multiple separate configuration files, reducing the overall system complexity while enabling comprehensive grayscale testing

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If separate rule configurations are made for each service, then each service can be tested independently, but the time required for configuration and testing increases

Engineering Contradiction:
Improveservice testing capabilityVSAvoidconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The grayscale testing rules for all services are pre-configured in the deployment descriptor before deployment. The configuration includes all necessary routing rules, version information, and traffic splitting parameters for service 1, service 2, service 3 and other services in advance, eliminating the need for time-consuming post-deployment configuration and enabling immediate testing

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple versions are deployed without environment isolation, then resource utilization improves, but version interference occurs and testing reliability decreases

Engineering Contradiction:
Improveresource utilizationVSAvoidtesting accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the deployment environment into isolated environments for different versions using namespace separation. Each version (e.g., version 1.0, version 2.0) is deployed in its own namespace, preventing interference between versions while allowing concurrent operation. The routing rules direct traffic to appropriate namespaces based on grayscale parameters, maintaining both resource efficiency and testing reliability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20230236954A1Information processing method and apparatus, computer device, and storage medium
Publication Date: 2023.07.27 TENCENT CLOUD COMPUTING (BEIJING) CO LTD
  • US20230236954A1 patent drawing
  • US20230236954A1 patent drawing
  • US20230236954A1 patent drawing

AI summary

A method of information processing includes obtaining a traffic request for a target service. The traffic request includes a request tag. The method further includes determining a target environment that matches with the request tag and obtaining first deployment information of the target service. The first deployment information of the target service indicates one or more test versions of the target service to be tested, and one or more corresponding environments respectively deployed for the one or more test versions of the target service. The method also includes determining, from the one or more test version, a target test version that is deployed to the target environment and accessing the target service in the target test version in the target environment. Apparatus and non-transitory computer-readable storage medium counterpart embodiments are also contemplated.