Global Traffic Manager for Non-Disruptive Cloud Instance Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based applications face disruptions during updates and additional instance deployments, causing downtime for end users, which is a technical challenge that existing methods have not adequately addressed.
Innovation Solution
Implementing a global traffic manager that routes requests based on geographic metadata, allowing for the deployment of additional instances without disrupting users by enabling and disabling endpoints dynamically, ensuring seamless access to cloud-based applications across multiple geographic regions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional deployment methods are used to update cloud applications or add instances, then updates and instance deployments can be completed, but service disruption and downtime occur for end users
Solution Approach 1:
The patent implements preliminary action by creating a new instance and configuring it with all necessary updates and components before it needs to go live. The new instance is prepared in advance with the latest software versions, configurations, and dependencies, so that when the switch occurs, the transition is immediate and seamless without requiring downtime for updates.
Solution Approach 2:
The patent uses an intermediary approach by introducing a DNS-based routing mechanism that acts as a mediator between end users and the cloud application instances. The DNS system redirects traffic from the old instance to the new instance, allowing the transition to occur without users directly experiencing the switch. This intermediary layer absorbs the transition smoothly, maintaining continuous service availability.
2Reliability
If additional instances are deployed to improve cloud service capacity and redundancy, then service reliability is enhanced, but deployment complexity and potential disruption increase
Solution Approach 1:
The patent applies segmentation by dividing the cloud application into multiple independent instances that can be deployed, managed, and updated separately. Each instance is a self-contained unit with its own resources and configuration, allowing parallel deployment without interfering with other instances. This segmentation reduces deployment complexity by making each instance manageable as an independent unit rather than requiring coordinated updates across a monolithic system.
Solution Approach 2:
The patent implements universality by creating a standardized instance deployment framework that can be applied repeatedly across multiple instances with consistent processes. The same deployment pipeline, configuration templates, and DNS routing mechanisms used for the first instance can be universally applied to subsequent instances, reducing the complexity of deploying additional instances by reusing established patterns rather than creating new procedures for each deployment.
3Productivity
If updates are deployed to cloud applications, then application functionality and performance are improved, but service disruption occurs during the update process
Solution Approach 1:
The patent implements preliminary action by completing all update operations, including software installation, configuration changes, and dependency updates, on the new instance before it becomes active. This ensures the updated instance is fully prepared and tested in advance, so when traffic is switched to it, the performance improvements are immediately available without any downtime for applying updates.
Solution Approach 2:
The patent maintains continuity of useful action by ensuring that while one instance is being updated, the other instance continues to serve user requests without interruption. The DNS routing system continuously directs traffic to the available instance, maintaining uninterrupted service delivery. This allows update operations to proceed in the background without breaking the continuous provision of cloud services to end users.
Data Source
AI summary
Methods, systems, and non-transitory computer-readable media are described herein. In some embodiments, a computing platform may deploy a cloud application comprising a first instance of the cloud application. Further, the computing platform may direct a DNS to the first instance of the cloud application. Next, the computing platform may determine that a second instance of the cloud application should be deployed. Additionally, the computing platform may create a first global traffic manager configured with at least a first endpoint and a second endpoint, where the first endpoint is associated with the first instance and is enabled, and where the second endpoint is associated with the second instance, and is disabled. Subsequently, the computing platform may direct the DNS to the first global traffic manager. The computing platform may then direct the DNS to the first global traffic manager, enable the second endpoint. In addition, the computing device may direct, based on metadata associated with each of a plurality of users, each of the plurality of users to one of the first instance and the second instance, wherein one or more users are directed to each of the first instance and the second instance.