Sidecar Container Integration for Reducing Duplicative Maintenance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software applications face challenges in efficiently integrating with computing environments due to duplicative implementation and maintenance complexities of integration functions, which require frequent recompilation and redeployment, leading to wasted resources and network complexity.

Innovation Solution

Implementing integration functions within separate sidecar containers that communicate with primary application containers via messaging calls, allowing multiple applications to share the same integration function instance, reducing the need for duplicative implementations and simplifying maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If integration functions are implemented within each application container, then each application can execute independently, but duplicative implementation and maintenance complexity increases

Engineering Contradiction:
ImproveIndependent application executionVSAvoidDuplicative implementation and maintenance
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a shared integration function that can serve multiple applications simultaneously. Instead of each application having its own copy of the integration function, a single shared integration function is instantiated and reused across multiple application containers, reducing duplicative implementation while maintaining independent application execution capability

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

Solution Approach 2:

The patent introduces a message queue as an intermediary component between applications and the shared integration function. Applications communicate their needs through the message queue, and the shared integration function processes these messages, enabling decoupled communication and reducing direct dependency complexity between applications

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If integration functions are recompiled and redeployed frequently, then integration updates can be applied, but resource waste and network complexity increase

Engineering Contradiction:
ImproveIntegration function updatesVSAvoidResource waste from frequent recompilation and redeployment
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

By implementing a single shared integration function that serves multiple applications, the system eliminates the need for frequent recompilation and redeployment of integration functions. The shared function is updated once and benefits all applications, significantly reducing resource waste associated with repeated builds and deployments

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

Solution Approach 2:

The patent implements a mechanism where the shared integration function is pre-loaded and ready to serve multiple applications. When applications need integration functionality, they can immediately use the pre-existing shared function without waiting for compilation or deployment, reducing resource consumption and update frequency

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple applications have separate integration function instances, then each application has dedicated resources, but network complexity increases

Engineering Contradiction:
ImproveDedicated resource allocationVSAvoidNetwork complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a shared integration function that can serve multiple applications simultaneously, reducing the number of network connections and communication paths required. Instead of each application having dedicated integration function instances that need to communicate with separate services, a single shared function handles all integration needs, simplifying network architecture

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

Data Source

PatentUS11915034B2Sidecar-based integration capabilities for containerized applications
Publication Date: 2024.02.27 RED HAT LLC
  • US11915034B2 patent drawing
  • US11915034B2 patent drawing
  • US11915034B2 patent drawing

AI summary

Methods and systems for improved integration functions for applications are provided. In one embodiment, a method is provided that includes receiving a request to execute an application. The request may specify a primary container image for the application and a secondary container image for an integration function used by the application. A primary container may be created for execution of the primary container image and a secondary container image separate from the primary container may be created for execution of the secondary container image. The primary and secondary containers may be executed to implement the application.