Bridge Container Virtualizing External Service Connections

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In legacy systems, connecting software inside containers to service instances running outside the container scope is difficult due to the need for hard-coding connection information, which lacks flexibility and requires shutdowns and restarts, disrupting service availability.

Innovation Solution

A bridge container monitors and detects connection information for service instances outside the container scope, initializing virtual containers to virtualize services, allowing source containers to access them without needing hard-coded information, enabling dynamic and flexible connections without service downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection information is hard-coded in containers to connect to service instances outside container scope, then connection stability is improved, but flexibility and adaptability deteriorate, requiring shutdowns and restarts when changes are needed

Engineering Contradiction:

Improveconnection stabilityVSAvoidconnection flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a service mesh infrastructure as an intermediary layer between containers and external service instances. This mesh includes service entries, virtual services, and endpoints that abstract the connection details. Containers connect to the service mesh rather than directly to external services, allowing the mesh to handle connection information dynamically without requiring container modifications or restarts when service instances change.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If connection information is hard-coded in containers, then connection reliability is improved, but device complexity increases due to the need to modify every container when service instances change

Engineering Contradiction:

Improveconnection reliabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts connection information and service discovery logic from individual containers and centralizes it in the service mesh infrastructure. The service mesh maintains service entries, endpoints, and routing rules externally, allowing containers to connect without embedding hard-coded connection details. This extraction reduces the complexity burden on individual containers while maintaining reliable connections through the centralized mesh.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If service instances are updated outside container scope, then service evolution is enabled, but service availability deteriorates due to required shutdowns and restarts

Engineering Contradiction:

Improveservice evolution capabilityVSAvoidservice availability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The service mesh implements dynamic service discovery and routing mechanisms that automatically adapt to service instance changes. When service instances are updated or replaced outside container scope, the mesh dynamically updates its endpoint configurations and routing rules without requiring container shutdowns or restarts. This dynamic adaptation maintains service availability while enabling continuous service evolution.

Inventive Principle:

Principle #15Dynamics

4Reliability

If containers are isolated from external service instances, then container security and portability are improved, but ease of operation deteriorates due to difficulty in connecting to external services

Engineering Contradiction:

Improvecontainer isolation securityVSAvoidconnection ease

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The service mesh acts as a secure intermediary that maintains container isolation while facilitating external service connections. Containers interact with external service instances through the mesh's abstractions (service entries, virtual services, endpoints) rather than direct connections. This intermediary layer preserves security boundaries and portability while simplifying connection operations through centralized service discovery and automatic connection management.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11416274B2Bridging a connection to a service by way of a container to virtually provide the service

Publication Date: 2022.08.16 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer-implemented method includes detecting, by a bridge container running inside a container scope, connection information about a first service instance running to provide a respective first service outside the container scope. A first virtual container is initialized inside the container scope. The first virtual container is connected to the first service instance, utilizing the connection information about the first service instance, to virtualize the first service instance inside the container scope. It is detected that that a first source container inside the container scope requires the first service of the first service instance. The first source container is connected to the first virtual container to enable the first source container to access the first service instance through the first virtual container.