Independent Cloud Pipelines for Live Data Validation Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods of deploying code in cloud environments introduce risks by testing new versions with live data, potentially affecting customers and requiring complex validation processes.

Innovation Solution

Deploying independent pipelines (IPs) in a cloud-based system, each with a different version of the service, allowing validation with real production data without impacting customers, and isolating each IP for debugging and security enforcement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If new versions of code are deployed and tested with live data in traditional methods, then validation with real production data is achieved, but customer environments are impacted and reliability decreases

Engineering Contradiction:
Improvevalidation accuracyVSAvoidcustomer environment stability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system segments the code validation process into isolated pipeline instances. Each pipeline instance processes a portion of customer data independently, allowing validation of new code versions without affecting the entire customer environment. This segmentation enables parallel validation while maintaining customer service stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces pipeline instances as intermediary components between the new code and customer environments. These instances act as buffers that allow validation traffic to flow through new code versions without directly impacting production customer services, thus protecting reliability while enabling measurement.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple pipeline instances are deployed for validation, then validation capability is improved, but device complexity increases

Engineering Contradiction:
Improvevalidation throughputVSAvoidpipeline management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates universal pipeline instances that can handle multiple functions: processing production data, validating new code versions, and maintaining customer service continuity. Each instance is designed to be multi-functional, reducing the need for separate specialized components and thereby managing complexity while improving validation productivity.

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

Solution Approach 2:

The system manages complexity by allowing dynamic parameter changes in pipeline instances, such as adjusting the volume of data processed, the version of code being validated, and the routing configuration. This flexibility enables the system to adapt to different validation scenarios without requiring fundamentally different architectural components.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If all traffic is routed through new code for validation, then comprehensive validation is achieved, but harmful factors increase

Engineering Contradiction:
Improvevalidation completenessVSAvoidcustomer impact
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

The patent implements partial routing of traffic through pipeline instances for validation. Instead of routing all customer traffic through new code versions, only a controlled portion is directed to validation pipelines, while the majority continues through stable production code. This partial action achieves sufficient validation completeness while minimizing harmful impacts on customers.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system prepares cushioning mechanisms in advance by maintaining stable production pipelines running parallel to validation pipelines. If validation issues arise, the system can immediately redirect traffic to the pre-prepared stable pipelines, cushioning the impact on customers before problems propagate.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS20250258749A1Systems and methods for deploying independent pipelines in a cloud-based system
Publication Date: 2025.08.14 ZSCALER INC
  • US20250258749A1 patent drawing
  • US20250258749A1 patent drawing
  • US20250258749A1 patent drawing

AI summary

Systems and methods for deploying independent pipelines in a cloud-based system include providing a service to a plurality of customers via a cloud-based system, wherein the service is adapted to receive requests and provide an output to perform a function for the plurality of customers; deploying one or more Independent Pipelines (IPs), wherein each of the one or more IPs comprises an instance of the service, and wherein the one or more IPs are independent of one another; feeding real production data through the service and each of the one or more IPs; and using an output from one of the service or any of the one or more IPs to perform the function of the service for the plurality of customers.