Service Testing Framework for SOA Dependency Reconfiguration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The staged installation of service-oriented architectures is time-consuming and prone to errors due to iterative deployments and frequent reconfigurations, which can lead to service instability and performance issues.

Innovation Solution

A service testing application is implemented to execute test operations, reconfigure service references, and traverse a dependency model to identify and remediate failing services, allowing dependent services to continue functioning by redirecting calls to corresponding services in another installation, thereby ensuring stability and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If staged installation is used to deploy services in new installations, then service stability can be maintained during deployment, but installation time and resource requirements increase significantly

Engineering Contradiction:
Improveservice stabilityVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing service testing and dependency analysis before actual deployment. The system identifies all service dependencies and potential failures in advance, allowing for pre-configured remediation strategies. This enables faster staged installation because the testing and validation work is done beforehand, reducing the time required during each deployment stage while maintaining service stability.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If frequent reconfigurations are performed to update service references during staged installation, then service dependencies can be updated, but error rates and resource consumption increase

Engineering Contradiction:
Improveservice reference updatesVSAvoiderror rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms by continuously monitoring service test results and dependency configurations during staged installation. When a service reference reconfiguration is performed, the system automatically tests the affected services and provides feedback on whether the reconfiguration was successful. This closed-loop feedback reduces error rates by detecting and correcting configuration errors immediately, rather than discovering them later when they cause service failures.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system applies self-service by automatically detecting service dependencies, performing reconfigurations, and validating changes without requiring manual intervention. The automated dependency model traversal and service reference updating reduce human errors while maintaining adaptability to changing service configurations during staged installation.

Inventive Principle:
Principle #25Self-service

3Reliability

If iterative testing and reconfiguration are performed to ensure service stability, then service performance can be validated, but resource requirements and installation complexity increase

Engineering Contradiction:
Improveservice stability validationVSAvoidinstallation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the service installation process into distinct, manageable stages: dependency identification, service reference reconfiguration, and targeted testing. Each stage focuses on a specific aspect of the deployment, reducing overall complexity. The dependency model is also segmented into individual service relationships, allowing for granular testing and reconfiguration of specific service pairs rather than testing the entire system repeatedly.

Inventive Principle:
Principle #1Segmentation

4Productivity

If all services are deployed collectively without staged installation, then installation time is reduced, but service stability and performance control are compromised

Engineering Contradiction:
Improveinstallation speedVSAvoidservice stability control
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent enables faster collective deployment by performing preliminary dependency analysis and service testing before deployment. The system identifies all service relationships and potential failures in advance, creating a deployment plan that allows services to be deployed collectively while maintaining stability control. This preliminary preparation eliminates the need for slow iterative testing during actual deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that monitor service stability during collective deployment. Automated testing validates service performance in real-time, providing feedback that allows the deployment process to continue at full speed while maintaining reliability control. This enables the benefits of collective deployment without sacrificing stability validation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9286179B1Service testing framework
Publication Date: 2016.03.15 AMAZON TECH INC
  • US9286179B1 patent drawing
  • US9286179B1 patent drawing
  • US9286179B1 patent drawing

AI summary

Disclosed are various embodiments for a service testing application. A service testing application executes test operations for services in a service-oriented architecture. If a test is failed, services that are dependent upon a failing service are reconfigured to instead call a corresponding service in a different installation of the service-oriented architecture. A dependency model of the service-oriented architecture may be searched to determine which service dependencies to reconfigure.