Service Registry Query Forwarding in SOA Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In service-oriented architecture (SOA) networks, finding services beyond local registries is challenging due to the limitations of centralized registries (single point of failure and scalability issues) and fully distributed registries (synchronization difficulties and network traffic problems).

Innovation Solution

A method and system that allow clients to search for services by forwarding queries to neighboring service registries based on properties other than the service being searched for, such as latency, geographic location, or bandwidth, in a network of service registries organized in tree or mesh topologies, enabling efficient service discovery while reducing network traffic and improving fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized service registry is used, then service discovery is simplified, but the system has single point of failure and scalability issues

Engineering Contradiction:
Improveservice discovery simplicityVSAvoidfault tolerance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The centralized service registry is segmented into multiple distributed service registries across different nodes in the network. Each registry maintains a portion of the service database, eliminating the single point of failure while preserving service discovery functionality through the peer-to-peer query forwarding mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Service registries act as intermediaries that forward queries to neighboring registries when services are not found locally. This mediator approach maintains the simplicity of service discovery by automatically routing queries through the network without requiring clients to understand the distributed architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a fully distributed service registry is used, then fault tolerance is improved, but synchronization difficulties and network traffic problems occur

Engineering Contradiction:
Improvefault toleranceVSAvoidsynchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each service registry maintains local control over its own service database portion, allowing independent operation and updates without requiring global synchronization. This local quality approach reduces synchronization complexity while maintaining fault tolerance through the distributed architecture.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial service discovery by first searching local registry databases before forwarding queries to neighbors. This partial action approach reduces overall network traffic by satisfying queries locally when possible, while still providing fault tolerance through the distributed structure.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If service queries are forwarded to all neighboring registries, then service discovery completeness is improved, but network traffic increases

Engineering Contradiction:
Improveservice discovery completenessVSAvoidnetwork traffic
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system performs partial query forwarding by first searching the local registry database and only forwarding queries to neighboring registries when services are not found locally. This partial action approach maintains service discovery completeness while significantly reducing network traffic by avoiding redundant queries to all neighbors for every service lookup.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Each service registry serves itself by first checking its own local database before forwarding queries to neighbors. This self-service approach reduces network traffic by handling local service discovery requests independently, while still providing complete service discovery through the fallback mechanism to neighboring registries.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9984158B2Finding services in a service-oriented architecture (SOA) network
Publication Date: 2018.05.29 AXIS
  • US9984158B2 patent drawing
  • US9984158B2 patent drawing
  • US9984158B2 patent drawing

AI summary

A method and system for finding services in a service-oriented architecture network may include receiving, in a local service registry from a client, a search query for a particular service. The local service registry may include a local database listing registered services. The network may include querying the local database to determine a first list of services that satisfy the search query and determining a neighboring service registry, in a network of service registries, based on a property other than a property of the particular service being searched for. The method may include sending the search query to the neighboring service registry and receiving, from the neighboring service registry, a second list of services, registered with the neighboring service registry, that satisfy the search query. The method may include returning, to the client, the first list of services and the second list of services that satisfy the search query.