Metadata Manager for Unified Cloud Account State Views

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale cloud computing environments, managing and debugging complex distributed systems with multiple services and resources across various data centers becomes increasingly difficult due to the complexity of understanding the state of client accounts, especially for large client accounts with fast-changing service subscriptions and resource allocations.

Innovation Solution

A metadata manager is implemented to aggregate and provide unified views of client account states across multiple services and resources, supporting features like account versioning, cloning, causal analysis, and simulation to help administrators comprehend and manage the environment effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud computing environments provide diverse distributed services with independently configurable implementation modules, then service versatility and customization are improved, but system complexity and difficulty of comprehension increase

Engineering Contradiction:
Improveservice versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the complex cloud environment into distinct service modules, each with its own schema definition. The metadata manager collects and organizes schema information from multiple independent services, allowing each service to be configured independently while maintaining overall system coherence through standardized metadata interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The metadata manager acts as an intermediary between diverse distributed services and the administrator. It collects schema information from various services, normalizes it into a unified structure, and presents it through a consistent interface, thereby reducing the complexity burden on administrators while preserving service versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If cloud environments support fast-changing service subscriptions and resource allocations, then operational flexibility is improved, but difficulty of debugging and comprehending root causes increases

Engineering Contradiction:
Improveoperational flexibilityVSAvoiddebugging difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system performs preliminary action by collecting and storing schema information from all services before problems occur. The metadata manager maintains a comprehensive record of service configurations and relationships, enabling administrators to quickly understand the state of the system during debugging without having to traverse complex real-time configurations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The metadata manager provides feedback mechanisms that enable administrators to query and analyze service configurations, resource allocations, and their relationships. This feedback loop allows for efficient debugging by presenting organized information about the current system state, making it easier to trace root causes of problems in fast-changing environments.

Inventive Principle:
Principle #23Feedback

3Difficulty of detecting and measuring

If administrators need detailed understanding of client cloud environment state, then debugging capability is improved, but administrative burden and time consumption increase

Engineering Contradiction:
Improvedebugging capabilityVSAvoidadministrative time
Core Design Contradiction:
Difficulty of detecting and measuringVSLoss of time

Solution Approach 1:

The metadata manager creates a simplified copy or representation of the complex cloud environment state through standardized schema information. This metadata copy captures essential relationships and configurations in an organized format, allowing administrators to understand the environment state quickly without having to manually investigate each service detail, thereby reducing administrative time while maintaining debugging capability.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8805971B1Client-specified schema extensions in cloud computing environments
Publication Date: 2014.08.12 AMAZON TECH INC
  • US8805971B1 patent drawing
  • US8805971B1 patent drawing
  • US8805971B1 patent drawing

AI summary

Methods and apparatus for client-specified schema extensions in cloud computing environments are disclosed. A system includes a plurality of service managers coordinating respective multitenant network-accessible services, and one or more computer servers. In response to a schema extension request specifying a client account, a client attribute set, and a client data source, the one or more computer servers generate a composite schema customized for the client account comprising (a) attributes of a plurality of resources implementing the functionality of at least one service to which the client account has access and (b) the client attribute set. In response to an account state view request specifying the client account, the one or more computer servers provide a state representation comprising (a) at least one value of a particular client attribute and (b) at least one attribute value of a resource.