Implanted Agent Microservice Routing via Distributed Hash Table

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing configuration management tools are not specifically designed for microservices routing configuration, requiring external platforms and central controllers, which limits flexibility and scalability, especially in applications with high churn rates or complex deployments.

Innovation Solution

A decentralized system where microservices manage their own routing using implanted agents and a distributed hash table (DHT) called Bitverse, allowing self-configuration of reverse proxies without external platform dependencies, enabling microservices to dynamically create clusters and manage load balancing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized configuration management tool is used to manage microservices routing, then the system provides centralized control and coordination, but the system complexity increases and scalability is limited

Engineering Contradiction:
Improvecentralized controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized configuration management function by distributing it across multiple implanted agents running in separate software containers. Each agent independently manages routing configuration for its associated microservice, eliminating the need for a single centralized controller and reducing system complexity while maintaining reliable configuration management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The implanted agents enable microservices to self-configure their routing by automatically registering with the DHT and managing their own proxy configurations. This self-service approach eliminates dependency on external platform services and reduces the complexity of centralized control mechanisms.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If external platform services are used for configuration management, then coordination is simplified, but dependency on external platforms increases and flexibility decreases

Engineering Contradiction:
Improvecoordination simplicityVSAvoidplatform independence
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a distributed hash table (DHT) as an intermediary data structure that enables agents to coordinate configuration management without relying on external platform services. The DHT provides a platform-independent mechanism for agents to discover and communicate routing information, maintaining operational simplicity while ensuring platform independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The implanted agent is designed as a universal component that can operate across different software container platforms and environments. It provides multiple functions including service registration, configuration management, and proxy configuration, eliminating the need for platform-specific services and increasing flexibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If microservices are frequently started and stopped with high churn rates, then dynamic scaling is improved, but configuration management complexity increases

Engineering Contradiction:
Improvedynamic scalingVSAvoidconfiguration management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic configuration management system where implanted agents automatically register and deregister microservices with the DHT based on their runtime state. When microservices are started or stopped, agents dynamically update the DHT, enabling automatic configuration updates without manual intervention and simplifying management of high-churn environments.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where implanted agents continuously monitor the state of their associated microservices and automatically update the DHT configuration accordingly. This feedback loop ensures that the routing configuration remains synchronized with the actual runtime state of microservices, simplifying management during frequent start-stop operations.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If a distributed hash table is used for configuration storage, then platform independence and flexibility are improved, but the complexity of configuration coordination increases

Engineering Contradiction:
Improveplatform independenceVSAvoidconfiguration coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The implanted agents autonomously manage their own configuration coordination by directly interacting with the DHT. Each agent independently performs service registration, configuration updates, and proxy configuration without requiring complex coordination protocols between multiple centralized components. This self-service approach simplifies configuration coordination while maintaining platform independence.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10785334B2Implanted agent within a first service container for enabling a reverse proxy on a second container
Publication Date: 2020.09.22 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US10785334B2 patent drawing
  • US10785334B2 patent drawing
  • US10785334B2 patent drawing

AI summary

It is presented a method performed by a first software container comprising an implanted agent, which is configured to run in said first software container. The method comprise the steps, performed by the implanted agent, of: resolving an Internet Protocol, IP, address and a port of the first software container; and registering a microservice identity, the IP address and the port of the first software container in a first distributed hash table for enabling a second implanted agent running in a second software container to configure a reverse proxy running in the second software container.