Trace Signature Generation for Service Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In service-oriented systems, managing and tracing requests across distributed networks is complex, leading to increased latency, resource usage, and security challenges due to the need for external tracing services and inefficient handling of requests based on call paths.

Innovation Solution

Implementing real-time call tracing through session-persisted trace signatures, where each service generates and modifies a unique identifier, allowing downstream services to make decisions based on tier data and Bloom filters, reducing the need for external consultations and maintaining signature size regardless of call path complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If external tracing services are used to manage requests across distributed networks, then request tracing capability is improved, but system latency and resource usage increase

Engineering Contradiction:
Improverequest tracing capabilityVSAvoidsystem latency
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts the tracing functionality from external services and embeds it directly into the service mesh infrastructure. Each service node maintains local tracing state through session-persisted trace signatures, eliminating the need to query external tracing services for every request, thus reducing latency while maintaining comprehensive tracing capability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements self-service tracing where each service node autonomously generates, modifies, and processes trace signatures without requiring external consultation. Services independently make decisions based on their local trace signature state, eliminating dependency on external tracing services and reducing overall system latency

Inventive Principle:
Principle #25Self-service

2Measurement precision

If external tracing services are used to manage requests across distributed networks, then request tracing capability is improved, but resource usage increases

Engineering Contradiction:
Improverequest tracing capabilityVSAvoidresource usage
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent extracts tracing operations from resource-intensive external services and implements them locally at each service node. Trace signatures are maintained in session memory with constant size regardless of call path complexity, eliminating the need for continuous external service communication and reducing overall resource consumption

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each service node performs self-service tracing by independently generating and processing trace signatures using local resources. This eliminates the need for external service consultations, reducing network traffic and computational overhead while maintaining comprehensive tracing capability

Inventive Principle:
Principle #25Self-service

3Measurement precision

If trace signature size increases to capture complex call paths, then tracing accuracy is improved, but performance degradation occurs

Engineering Contradiction:
Improvetracing accuracyVSAvoidperformance
Core Design Contradiction:
Measurement precisionVSSpeed

Solution Approach 1:

The patent changes the parameter of trace signature size from variable (based on call path complexity) to constant. Each trace signature maintains a fixed size regardless of the number of services in the call path, ensuring consistent performance characteristics while capturing complete tracing information through efficient encoding schemes

Inventive Principle:
Principle #35Parameter changes

4Device complexity

If traditional request handling is used without call path awareness, then system simplicity is maintained, but security and priority-based decision-making are compromised

Engineering Contradiction:
Improvesystem simplicityVSAvoidsecurity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements preliminary action by encoding call path information into trace signatures that are processed in real-time as requests traverse the service mesh. Services make security and priority decisions based on pre-computed trace signature data before executing request handling logic, enabling proactive security measures without complex post-processing

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The trace signature acts as an intermediary carrier that conveys call path information between services. This intermediary mechanism enables services to make informed security and priority decisions without requiring complex inter-service communication or centralized control, maintaining system simplicity while enhancing security capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10554701B1Real-time call tracing in a service-oriented system
Publication Date: 2020.02.04 AMAZON TECH INC
  • US10554701B1 patent drawing
  • US10554701B1 patent drawing
  • US10554701B1 patent drawing

AI summary

Methods, systems, and computer-readable media for real-time call tracing in a service-oriented system are disclosed. A request comprising a trace signature is received at a service in a service-oriented system. The trace signature comprises a representation of one or more upstream services in an upstream call path associated with the request. Based at least in part on the trace signature, the service determines one or more actions to perform with respect to the request.