Service Mesh Offload to Network Interface Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The sidecar communication model for microservices introduces latency in service-to-service communications, which is problematic for latency-sensitive applications like 5G control planes, as existing solutions such as Linux implementations of eBPF do not ensure predictable communication transmission times.
Innovation Solution
Offloading service mesh sidecars to an Infrastructure Processing Unit (IPU) or Data Processing Unit (DPU), which schedules packet transmissions at specific time slots to reduce unexpected delays and provides more predictable latency by controlling packet transmission times, thereby reducing latency in service-to-service communications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If sidecar communication model is used for microservices, then service-to-service communications are facilitated, but latency is introduced in communications
Solution Approach 1:
The patent extracts the sidecar proxy functionality from the traditional software-based implementation and relocates it to a network interface device (NIC). This hardware-level extraction eliminates the latency introduced by software-based sidecars while maintaining their communication facilitation capabilities. The NIC directly handles packet routing and service mesh operations without the processing overhead of conventional software proxies.
Solution Approach 2:
The patent replaces the software-based mechanical system (sidecar proxy running on host CPU) with a hardware-based system (network interface device). This substitution moves communication management from the software layer to the hardware layer, enabling faster packet processing and reducing latency while preserving the service mesh communication facilitation function.
2Extent of automation
If Linux implementations of eBPF are used, then sidecar operations can be performed, but predictable communication transmission times are not ensured
Solution Approach 1:
The patent replaces the software-based eBPF implementation with a hardware-based network interface device. This substitution provides deterministic and predictable packet transmission timing because hardware NICs operate at the physical layer with fixed timing characteristics, eliminating the variability introduced by Linux scheduling and software processing in eBPF implementations.
3Loss of time
If service mesh sidecars are offloaded to network interface device, then latency is reduced, but device complexity increases
Solution Approach 1:
The patent implements multi-functionality in the network interface device by enabling it to perform both traditional network functions (packet routing, switching) and service mesh sidecar operations (traffic management, service discovery, load balancing). This universal approach consolidates multiple functions into a single device, reducing overall system complexity while achieving latency reduction through hardware acceleration.
Data Source
AI summary
Examples described herein relate to a system for offloading microservice-to-microservice communication to a network interface device.