Sidecar Adapter Container for Software-Defined Networking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The frequent polling of services by third-party solutions through API gateways in software-defined networking environments leads to significant load on the API gateway and computing environment, causing inefficiencies and potential delays in updating network configurations.
Innovation Solution
Integrating a sidecar adapter container within service instances to receive push notifications or directly poll the main container, reducing the need for third-party solutions to rely on API gateways for information updates and improving real-time awareness of changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If third party solutions frequently poll services through API gateways to obtain network information, then real-time awareness of network changes is improved, but the load on API gateway and computing environment increases significantly
Solution Approach 1:
The system implements event-driven architecture where service instances publish configuration changes to an event bus, and third-party solutions subscribe to receive notifications only when changes occur. This feedback mechanism ensures real-time awareness of network changes while eliminating continuous polling load on the API gateway.
Solution Approach 2:
Service instances autonomously publish their own configuration changes to the event bus without requiring third-party solutions to actively poll. The system self-notifies interested parties of changes, shifting the burden from continuous polling to event-driven communication.
2Loss of information
If third party solutions poll services regularly to obtain configuration information, then information freshness is improved, but system complexity and polling overhead increase
Solution Approach 1:
The event bus system establishes a push-based feedback mechanism where service instances automatically notify subscribers of configuration changes. This eliminates the need for complex polling schedules and timing mechanisms, simplifying the information refresh approach while maintaining freshness.
Solution Approach 2:
Third-party solutions pre-subscribe to relevant events on the event bus, preparing to receive notifications in advance. When changes occur, the system is already configured to push information to subscribed clients, eliminating the need for complex polling logic.
3Loss of information
If API gateway handles frequent polling requests from third party solutions, then information availability is improved, but processing time and response delays increase
Solution Approach 1:
The event-driven architecture implements asynchronous push notifications where service instances directly publish changes to the event bus, which then notifies third-party solutions. This eliminates synchronous polling cycles through the API gateway, reducing processing time and response delays while maintaining information availability.
Solution Approach 2:
The event bus acts as an intermediary between service instances and third-party solutions, decoupling the direct request-response cycle through the API gateway. This mediator enables efficient information transfer without the processing overhead of frequent polling requests.
Data Source
AI summary
Certain embodiments described herein are directed to a method of receiving information associated with a service provided by a management plane for managing a remote network. The method, in one example, includes registering, at an adapter container, with a data store or an entity within a service instance of a service deployment associated with a service within a software-defined networking environment associated with the remote network, wherein the service is provided for managing a remote network, and wherein registering with the data store or the entity causes the data store or the entity to send information associated with the service instance to the adapter when information is available. The method also includes receiving, at the adapter container, information from the data store or the entity. The method also includes transforming the information from a first format to a second format. The method also includes transmitting the information to an endpoint.