Intelligent EPP Service Routing via Virtual IP Many-to-Many Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing systems for routing requests over the Extensible Provisioning Protocol (EPP) face challenges in efficiently managing domain name-related services, particularly in supporting version testing, upgrades, and rollbacks, while maintaining operational efficiency and cost-effectiveness.
Innovation Solution
The implementation of an intelligent routing system that includes multiple frontend service interfaces, gateways, and a backend service platform, utilizing virtual IP addresses (VIPs) for a many-to-many mapping, allowing for versioning and operational state management to support seamless service upgrades and rollbacks, and applying differentiated client policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dedicated service connection is maintained between each registrar and registry, then service reliability is improved, but device complexity and infrastructure costs increase
Solution Approach 1:
The system segments the connection architecture by introducing a gateway layer between registrars and registries. Each registrar connects to multiple gateways, which in turn connect to multiple registries, creating a segmented many-to-many topology that reduces direct connection complexity while maintaining service reliability through distributed access paths
Solution Approach 2:
The gateway is designed as a universal intermediary that can serve multiple registrars and registries simultaneously. The gateway handles diverse EPP protocol communications, versioning, and routing functions for different clients, eliminating the need for dedicated point-to-point connections while maintaining reliable service delivery
2Adaptability or versatility
If version testing and upgrades are supported for backend services, then service adaptability is improved, but device complexity increases
Solution Approach 1:
The system performs preliminary actions by maintaining version information and operational states (testing, current, next, rollback) for backend services in advance. The gateway is pre-configured with versioning logic that automatically selects appropriate service versions based on client requirements, enabling seamless version testing and upgrades without increasing operational complexity
Solution Approach 2:
The routing system dynamically adapts to different service versions and operational states through the gateway's intelligent routing decisions. The system can switch between service versions, test new versions, perform rollbacks, and manage multiple concurrent versions based on real-time needs, providing flexibility without requiring complex manual intervention
3Device complexity
If multiple backend services are accessed through a single gateway, then device complexity is reduced, but routing precision and service selection difficulty increase
Solution Approach 1:
The gateway incorporates feedback mechanisms that monitor service operational states, client preferences, and routing effectiveness. Based on this feedback, the gateway dynamically adjusts routing decisions to select appropriate backend services, maintaining precise service selection while simplifying the overall infrastructure through centralized management
Data Source
AI summary
Method and system for routing EPP requests over a network are provided. A routing system includes multiple frontend service interfaces, one or more gateways, a management server, and a backend service platform that provides multiple application services. The frontend service interfaces are addressable using virtual IP addresses (“VIP”) and can be provided by the gateways. The routing system defines a many-to-many mapping between the frontend service interfaces and a set of services provided by the backend service platform. A requestor can send a request over EPP to a targeted service interface to access one or more backend services, by sending the request to a target IP or domain name that corresponds to a VIP associated with the targeted service interface. Using the many-to-many mapping and the VIP of the targeted service interface, the routing system can identify backend services sought by the request and provide the requestor with access to the backend services.