Datacenter Service Table Routing for Dynamic Horizontal Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing datacenter scaling methods, such as vertical and horizontal scaling, face challenges in load balancing and security, particularly with load balancing switches needing to decrypt and re-encrypt network traffic, which complicates network management and security.
Innovation Solution
Implementing a datacenter system with a service table that stores route information from a signaling mechanism and a forwarding engine to route service requests, allowing for dynamic service advertisement and intelligent load balancing decisions, enabling end-to-end horizontal scalability and secure network traffic management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If load balancing switches are used to inspect network traffic for intelligent routing decisions, then load balancing capability is improved, but device complexity and security management deteriorate due to decryption and re-encryption requirements
Solution Approach 1:
The patent extracts the load balancing decision-making function from the network core (load balancing switches) and relocates it to the network edges (end hosts). This is achieved by implementing service tables and forwarding engines directly on end hosts, which autonomously make routing decisions based on service advertisements received via signaling protocols, eliminating the need for centralized traffic inspection and decryption at load balancing switches.
Solution Approach 2:
The patent introduces service tables as an intermediary data structure that stores service advertisement information and routing decisions. These service tables reside on end hosts and act as local mediators that translate service advertisements into forwarding decisions, eliminating the need for complex real-time communication with centralized load balancing switches and their associated decryption/re-encryption infrastructure.
2Reliability
If load balancing switches decrypt and re-encrypt network traffic for inspection, then security is improved, but productivity and energy efficiency deteriorate due to the overhead of decryption and re-encryption operations
Solution Approach 1:
The patent performs service advertisement and route information distribution in advance through signaling protocols before actual data traffic needs to be routed. Service tables are pre-populated with routing information, allowing end hosts to make immediate forwarding decisions without requiring real-time decryption or security inspection during data plane operations, thus eliminating the productivity overhead.
3Adaptability or versatility
If load balancing switches are reconfigured each time servers are added to the datacenter, then adaptability is improved, but loss of time and productivity deteriorate due to reconfiguration overhead
Solution Approach 1:
The patent implements a feedback mechanism where end hosts actively receive service advertisements from servers through signaling protocols. When new servers are added to the datacenter, they automatically advertise their services, and receiving end hosts update their service tables accordingly. This continuous feedback loop enables automatic adaptation to dynamic server additions without manual reconfiguration or centralized control plane intervention.
Solution Approach 2:
The patent enables end hosts to autonomously manage their own routing tables and forwarding decisions based on service advertisements they receive. Each end host independently processes service advertisements, updates its service table, and adjusts its forwarding behavior without requiring external reconfiguration, thereby achieving self-service adaptation to network changes.
Data Source
AI summary
A datacenter system including a plurality of nodes configured to send and receive a service request, a service table on the plurality of nodes configured to store route information extracted from a signaling mechanism, and a forwarding engine configured to route the service request to at least one of the plurality of nodes using route information from the service table.