Distributed Trace Storage for Service-Oriented Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As distributed systems grow in scale and complexity, managing and provisioning resources becomes increasingly complicated, especially in service-oriented architectures where monitoring and storing trace data across multiple services is inefficient, leading to resource wastage and management challenges.

Innovation Solution

Implementing distributed trace storage within individual services, where trace data is locally stored until expiration or space is needed, and only selected data is transmitted to a centralized analysis system, optimizing network and computing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If trace data is stored in a centralized location for all services, then data retrieval and analysis are simplified, but network bandwidth and centralized storage resources are excessively consumed

Engineering Contradiction:
Improvedata retrieval and analysisVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent segments the centralized trace storage system into distributed storage units at each service host. Each service stores its own trace data locally, eliminating the need to transmit all trace data across the network to a central location. This segmentation reduces network bandwidth consumption while maintaining the ability to retrieve and analyze trace data through the traceability index structure that links trace data across multiple services.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If all trace data is retained indefinitely for complete analysis, then analytical completeness is improved, but storage resource consumption increases

Engineering Contradiction:
Improveanalytical completenessVSAvoidstorage resource consumption
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent implements parameter changes by introducing expiration times for trace data. The trace data management system automatically removes trace data after a specified time period or when storage thresholds are reached. This parameter change maintains analytical completeness within the retention period while significantly reducing long-term storage resource consumption through automated data lifecycle management.

Inventive Principle:
Principle #35Parameter changes

3Loss of energy

If trace data is stored locally at each service host, then network bandwidth is reduced, but system complexity increases

Engineering Contradiction:
Improvenetwork bandwidth consumptionVSAvoiddistributed storage management
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a standardized trace data storage and management framework that can be implemented across all service hosts in the distributed system. The traceability index structure and expiration time mechanisms provide universal functionality that simplifies distributed storage management while maintaining the ability to retrieve and analyze trace data across service boundaries.

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

4Stability of the object's composition

If centralized components receive and store all trace data, then data consistency is maintained, but processing overhead and resource usage increase

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent implements preliminary action by having services store trace data locally at the source before any analysis is needed. This preliminary local storage eliminates the need for centralized data collection and processing, significantly improving processing efficiency while maintaining data consistency through the traceability index that preserves the relationships between trace data from different services.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10397343B1Distributed trace storage in a service-oriented system
Publication Date: 2019.08.27 AMAZON TECH INC
  • US10397343B1 patent drawing
  • US10397343B1 patent drawing
  • US10397343B1 patent drawing

AI summary

Methods, systems, and computer-readable media for implementing distributed trace storage in a service-oriented system are disclosed. A plurality of trace events are generated for a plurality of service interactions between individual ones of a plurality of services. The services are implemented by a plurality of hosts. Individual ones of the trace events comprise respective trace identifiers. The trace events are stored at individual ones of the hosts at which the respective trace events were generated. In response to a request from a trace analysis system, a portion of the trace events are retrieved and sent from individual ones of the hosts to the trace analysis system.