Dynamic Route Topography Management for Service Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In service-oriented architecture environments, testing development services against production services is challenging due to difficulties in modifying server routing information, which can lead to incorrect data and customer dissatisfaction, and changing DNS services can be cumbersome and slow to propagate.
Innovation Solution
A system and method for dynamically creating and modifying route topographies for software applications by assigning communication identifiers to services, allowing developers to clone routes, modify communication identifiers, and deploy services in cloud-based infrastructure for testing and integration purposes, using a routing service that manages route topography information and caching for efficient communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DNS services are used to manage server routing information, then services can be routed correctly, but changes to routing information are slow to propagate and cumbersome to modify
Solution Approach 1:
The system segments routing information into route topography data that can be independently managed and modified without affecting the entire DNS infrastructure. Each route topography represents a specific service endpoint configuration that can be updated separately, enabling granular control and faster propagation of changes.
Solution Approach 2:
The patent introduces route topography as an intermediary layer between application services and DNS services. This intermediary allows routing information to be managed and modified without directly changing DNS records, thus maintaining routing accuracy while enabling easier and faster modifications through a dedicated management interface.
2Reliability
If development services are tested against production services, then integration testing can be performed, but routing complexity increases and testing reliability may be compromised
Solution Approach 1:
The system creates route topography copies that represent different service environments (development, production, testing). These copied route configurations allow developers to test development services against production services by selecting appropriate route topography versions, enabling realistic integration testing without the complexity of managing multiple physical environments.
Solution Approach 2:
The patent adds a routing dimension through route topography that separates logical service routing from physical server locations. This additional dimension allows flexible routing configurations for testing scenarios without increasing physical infrastructure complexity, enabling developers to switch between different service endpoints through software configuration rather than physical reconfiguration.
3Adaptability or versatility
If server routing information is changed to point to development servers, then development testing can occur, but changes require DNS modification or application code changes which are cumbersome
Solution Approach 1:
The system implements dynamic route topography management where routing information can be changed at runtime without modifying application code or DNS records. Developers can switch between development and production environments by updating route topography configurations, enabling flexible environment switching through a centralized management interface that propagates changes automatically.
Data Source
AI summary
A system, method, and computer-readable medium are provided for managing a route topography in a software environment. The system includes a dashboard user interface for allowing a user to manage the services that are part of a software application. The dashboard allows the user to add and delete services for a software application, to establish a communication identifier of each service, and to clone a first route topography to create a second route topography. A routing service manages the route topography by storing a route identifier and the associated services for the route. When a user modifies an existing route topography or creates a new route topography, the information is managed by the routing service which provides the route information to requesting services upon demand. In one embodiment, each service of the software application includes a route cache with routing information that may be updated periodically by the routing service.