Service Discovery Manager for Cloud Load Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-based service architectures, service address changes due to restarts, data center failures, or load-balancing cause delays and increased load on DNS servers, making it time-consuming for users to access services as they need to query DNS servers for updated service locations.
Innovation Solution
Implementing a system with a Service Discovery Manager (SDM) that monitors service availability and communicates real-time or near-real-time service address changes to client devices, allowing them to update local databases with current service addresses, enabling seamless access to services through geographical redundancy and failover to alternative data centers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service address changes are registered at a central DNS server, then service location updates are achieved, but DNS server load increases and response time slows down
Solution Approach 1:
The patent segments the centralized DNS update function into distributed service registry components. Each service instance maintains its own registry information locally, eliminating the need for centralized DNS updates and reducing DNS server load while maintaining reliable service location tracking.
Solution Approach 2:
The patent introduces a service registry as an intermediary between services and clients. This registry maintains service location information and provides updates directly to clients without involving DNS servers, thereby reducing DNS query load while ensuring reliable service location updates.
2Reliability
If DNS TTL values are used for service address updates, then service redirection is achieved, but access delay occurs up to TTL time or longer
Solution Approach 1:
The patent implements preliminary action by having clients proactively subscribe to service registry updates before service address changes occur. The service registry maintains current service location information and pushes updates to subscribed clients in real-time, eliminating the need to wait for DNS TTL expiration and enabling immediate service access after address changes.
3Reliability
If service address changes are propagated through DNS, then service location updates are achieved, but the process becomes time-consuming for users
Solution Approach 1:
The patent implements feedback by establishing a subscription-based update mechanism where clients register their interest in specific services with the service registry. When service address changes occur, the registry immediately notifies subscribed clients, providing real-time feedback instead of relying on time-consuming DNS propagation processes.
Solution Approach 2:
The service registry acts as an intermediary that directly communicates service location changes to clients, bypassing the DNS propagation process entirely. This intermediary mechanism enables immediate service address updates without the time delays inherent in traditional DNS-based propagation.
Data Source
AI summary
A method may include identifying a service discovery manager associated with a first data center and registering with the service discovery manager. The method may also include, transmitting, by the service discovery manager, information identifying first services that are available at the first data center and information identifying a second data center in which one or more of the first services are available. The method may further include receiving the information identifying the first services that are available and the information identifying the second data center and updating a database based on the information identifying the first services that are available.