SOA Circuit Breaker for Downstream Failure Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex Service-Oriented Architecture (SOA) systems face challenges in managing and recovering from failures, particularly due to the difficulty in identifying and isolating performance issues within large, interconnected systems, leading to operational overhead and potential data loss.

Innovation Solution

A system management module with a circuit breaker mechanism is implemented to detect downstream service failures, prevent further requests from entering the affected system, and automatically suspend upstream components, thereby reducing operational overhead and backlog.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the system continues to process requests during downstream service failures, then request throughput is maintained, but system resource utilization increases and data loss occurs

Engineering Contradiction:
Improverequest throughputVSAvoidsystem resource utilization
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The circuit breaker mechanism proactively prevents requests from being routed to failed downstream services by monitoring failure patterns and automatically opening the circuit when threshold criteria are met. This preliminary action stops the harmful flow of requests before they can consume system resources, directly resolving the contradiction between maintaining throughput and preventing resource exhaustion.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The circuit breaker acts as an intermediary component between upstream services and downstream services, intercepting requests and deciding whether to allow them to proceed based on the circuit state. This mediator prevents direct interaction between failing services and healthy upstream services, reducing resource utilization while maintaining overall system productivity through selective request routing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system allows requests to propagate through failed services, then service availability is maintained, but operational overhead increases

Engineering Contradiction:
Improveservice availabilityVSAvoidoperational overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The circuit breaker implementation is self-managing, automatically detecting failures, making decisions about circuit state transitions, and managing its own configuration parameters. This self-service capability eliminates the need for complex external monitoring and manual intervention systems, reducing operational overhead while maintaining service availability through automated failure response.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The circuit breaker continuously monitors downstream service responses and uses this feedback to dynamically adjust its state (closed, open, half-open). This feedback mechanism enables the system to automatically adapt to changing service conditions without increasing operational complexity, maintaining availability while simplifying failure management through rule-based automated responses.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If the system implements comprehensive failure monitoring, then detection accuracy improves, but system complexity increases

Engineering Contradiction:
Improvefailure detection accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The circuit breaker implementation focuses monitoring efforts locally at each service boundary rather than implementing global system-wide monitoring. Each circuit breaker independently tracks failures for its specific downstream service using simple counters and thresholds, achieving accurate failure detection for that specific service without the complexity of comprehensive system-wide monitoring infrastructure.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10157092B2Automatic targeted system suspension based upon downstream system failure detection
Publication Date: 2018.12.18 ORACLE INT CORP
  • US10157092B2 patent drawing
  • US10157092B2 patent drawing
  • US10157092B2 patent drawing

AI summary

Techniques described herein relate to automatic system suspension based upon downstream system failure in service-oriented architecture (SOA) applications. A system management module of a SOA system may be configured to detect a problem with a downstream service provider involved with a SOA application, and in response, automatically suspend particular processing within the application to prevent requests that may end up at the downstream service provider from entering the SOA application. The system management module may implement a circuit breaker module that maintains a circuit breaker structure specific to a downstream endpoint leading to a downstream service provider. Upon a triggering of a circuit breaker for a downstream endpoint, one or more upstream service providers are identified as associated with faulted traffic causing the triggering, and the system management module can automatically cause further traffic from these upstream service providers to be suspended.