Hostname Resolution Management for Blue-Green Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blue-green deployment, when switching between old and new systems, there is a time lag in synchronizing IP address settings across multiple DNS servers, leading to instances where clients may access both systems, making it unclear which system is being accessed and potentially resulting in API calls to the old system from an HTML screen provided by the new system.
Innovation Solution
A management server system that communicates with DNS servers and a distribution server to manage IP address settings for hostnames, ensuring that API requests are routed to the new system before HTML requests, by rewriting IP addresses in a controlled manner to prevent API calls to the old system from the new system's HTML screen.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP address settings are synchronized across multiple DNS servers during system switching, then service continuity is maintained, but there is a time lag causing clients to access both old and new systems simultaneously
Solution Approach 1:
The patent segments the hostname resolution process into two distinct parts: HTML request hostname and API request hostname. By separating these resolution paths, the system can control which hostname resolves to which IP address independently, allowing API requests to be directed to the new system while HTML requests remain directed to the old system during the transition period.
Solution Approach 2:
The patent introduces a new dimension of control by using different hostnames for different request types (HTML vs API). This dimensional separation allows the system to manage traffic routing to old and new systems independently based on request type, rather than relying solely on time-based DNS synchronization.
2Productivity
If clients are allowed to access both old and new systems during transition, then service availability is maintained, but it becomes unclear which system is being accessed leading to potential API calls to the old system from new system's HTML screen
Solution Approach 1:
The patent segments the hostname resolution process into two distinct parts: HTML request hostname and API request hostname. By separating these resolution paths, the system can control which hostname resolves to which IP address independently, allowing API requests to be directed to the new system while HTML requests remain directed to the old system during the transition period.
Solution Approach 2:
The patent performs preliminary configuration by setting up separate hostname resolutions for HTML and API requests before the system switch. This preliminary action ensures that when the switch occurs, the routing is already predetermined and controlled, preventing the mixing of old and new system accesses.
3Reliability
If separate hostname resolutions are implemented for HTML and API requests, then precise control over system routing is achieved, but DNS server configuration complexity increases
Solution Approach 1:
The patent introduces a new intermediary component - a hostname resolution management system that sits between the DNS servers and the clients. This intermediary manages the separate hostname resolutions for HTML and API requests, coordinating with DNS servers to provide precise routing control without requiring direct complex configuration of each DNS server.
Data Source
AI summary
API hostnames and HTML hostnames are separately defined, and DNS switching for HTML is performed after a time lag from completion of DNS switching for APIs. APIs of old version are thereby prevented from being called from HTML screens of new version.