Cross-Cloud Traffic Splitting via Third Application Delivery Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software load balancers are limited to managing data traffic split and performance analytics within a single computing cloud, failing to provide these services between different cloud providers, which is necessary for customers to select optimal cloud infrastructure based on price, performance, and availability.
Innovation Solution
A system comprising a first application delivery controller (ADC) for each computing cloud and a third ADC to manage data traffic split between them, allowing blue/green deployment policies and traffic split policies across different cloud providers, such as Google Cloud Platform, Amazon Web Services, and Microsoft Azure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing software load balancers are used, then data traffic split and performance analytics can be managed within a single computing cloud, but they cannot provide these services between different cloud providers
Solution Approach 1:
The system segments the load balancing function by deploying separate ADC instances in each computing cloud (first ADC in first cloud, second ADC in second cloud) and introducing a third ADC to coordinate between them. This segmentation allows each ADC to operate independently within its cloud while the third ADC provides cross-cloud orchestration, resolving the limitation of single-cloud load balancers without requiring a completely complex monolithic architecture.
Solution Approach 2:
The third ADC acts as an intermediary between the first ADC and second ADC, receiving data traffic intended for applications in either cloud and routing it appropriately. This mediator approach enables cross-cloud traffic management by providing a coordination layer that translates external traffic requests into cloud-specific routing decisions, thereby achieving multi-cloud adaptability without directly modifying the internal architecture of each cloud's load balancer.
2Adaptability or versatility
If a third ADC is introduced to manage traffic between clouds, then cross-cloud data traffic split is enabled, but system complexity increases
Solution Approach 1:
The system divides the load balancing functionality across multiple ADC instances, with the first and second ADCs handling cloud-specific traffic and the third ADC handling cross-cloud coordination. This segmentation enables multi-cloud deployment capability while distributing complexity across manageable, independent components rather than creating a single monolithic complex system.
Solution Approach 2:
The third ADC is designed with multi-functionality, serving as a universal coordinator that can route traffic to either the first ADC or second ADC based on the destination cloud. This universal approach allows a single ADC instance to perform multiple routing functions across different clouds, reducing the need for additional specialized components and thereby limiting the increase in overall system complexity.
3Ease of operation
If load balancing is performed within a single cloud, then implementation is simple, but customers cannot select optimal cloud infrastructure based on price, performance, and availability
Solution Approach 1:
The third ADC serves as an intermediary that receives external traffic and intelligently routes it to the first ADC or second ADC based on cloud-specific conditions such as price, performance, and availability. This mediator architecture provides cloud selection flexibility by enabling dynamic routing decisions without requiring customers to manually configure complex routing rules, thereby maintaining ease of operation while achieving multi-cloud optimization.
Solution Approach 2:
The traffic routing architecture is made dynamic through the third ADC's ability to adaptively route traffic based on real-time cloud conditions. The system can dynamically adjust routing decisions according to changing price, performance, and availability metrics of different clouds, providing operational flexibility without requiring customers to manually reconfigure the system, thus balancing ease of operation with adaptive cloud selection capability.
Data Source
AI summary
Data traffic splitting between computing clouds may include a first application delivery controller (ADC) and a second ADC. The first ADC can be configured to control data traffic split within a first computing cloud. The second ADC can be configured to control data traffic split within a second computing cloud. The system may include a third ADC configured to control traffic split between at least the first ADC and the second ADC. The first ADC can be associated with a first version of an application configured to run on the first computing cloud. The second ADC can be associated with a second version of the application configured to run on the second computing cloud. The third ADC is further configured to control data traffic split based on at least one blue/green policy.