Publishable Metadata for Live Component Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web content management systems face challenges in testing new components in a live environment, as extensive offline testing often fails to simulate real-life usage and identify potential issues accurately, leading to difficulties in troubleshooting and deployment.

Innovation Solution

The implementation of publishable metadata that includes tags or identifiers to selectively direct content processing between existing and new components within a web content management system, allowing for dynamic switching between processing components and rendering controls based on metadata associated with content, enabling testing and load balancing in a live environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If new components are deployed to live environment for testing, then real-life usage data can be obtained and components can be tested accurately, but system stability and reliability may be compromised due to potential issues with untested components

Engineering Contradiction:
Improvecomponent testing reliabilityVSAvoiddeployment speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments content processing into different pipelines (existing pipeline and new pipeline) that can be independently activated. By dividing the content processing path, the system can route specific content through new components for testing while maintaining stable existing components for other content, thus testing reliability without compromising overall system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic switching between existing and new processing pipelines through metadata configuration. The system can dynamically adjust which pipeline handles which content based on real-time needs, allowing flexible testing of new components while maintaining system reliability through dynamic load distribution.

Inventive Principle:
Principle #15Dynamics

2Measurement precision

If extensive offline testing is performed before deployment, then component readiness can be verified, but real-life usage scenarios cannot be accurately simulated and potential issues remain undetected

Engineering Contradiction:
Improvetesting accuracyVSAvoidreal-life usage simulation
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent introduces metadata as an intermediary mechanism that enables selective routing of content to different processing pipelines. This intermediary allows the system to simulate real-life usage by routing actual user traffic through new components in controlled manner, providing accurate testing that mirrors real-world conditions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the content management system multi-functional by enabling it to handle both existing content through established pipelines and new content through testing pipelines simultaneously. This universality allows the system to serve dual purposes: maintaining stable service while providing accurate real-life testing capability.

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

3Stability of the object's composition

If new components are withheld from live environment until fully ready, then system stability is maintained, but troubleshooting and identifying issues becomes difficult

Engineering Contradiction:
Improvesystem stabilityVSAvoidtroubleshooting difficulty
Core Design Contradiction:
Stability of the object's compositionVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality by allowing different content to be processed through different pipelines based on specific content characteristics or metadata tags. This enables selective testing of new components for specific content types while maintaining stable processing for other content, thus preserving overall system stability while enabling targeted troubleshooting.

Inventive Principle:
Principle #3Local quality

4Productivity

If traffic is dynamically directed between existing and new components, then load balancing and incremental scaling can be achieved, but system complexity increases due to metadata management and switching mechanisms

Engineering Contradiction:
Improveload balancing capabilityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a copy of the existing content processing pipeline as a separate new pipeline. This copying approach allows independent development and testing of new components while maintaining the original pipeline as a stable baseline. The metadata management and switching mechanisms, while adding complexity, enable sophisticated load balancing and incremental scaling capabilities.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9058333B2Publishable metadata for content management and component testing
Publication Date: 2015.06.16 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9058333B2 patent drawing
  • US9058333B2 patent drawing
  • US9058333B2 patent drawing

AI summary

Techniques related to publishable metadata for content management are described that enable selective invocation of new components in a web content management system. Metadata that is published in connection with corresponding content can be configured to include tags or other identifiers that cause a content management system to selectively direct content processing between existing and new components. Switches implemented by the content management system can operate to examine the metadata to determine which processing components are selected for particular content and direct the content to corresponding components. Switches can also be placed in websites to direct page requests from clients to existing or new rendering controls based upon publishable metadata that is associated with a requested page. Thus, the metadata and switches can be employed to perform testing of and load balancing between new and existing components in a live environment.