Container Cluster Data Sharing via Logical Namespace

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional PaaS cloud platforms using Docker containers face challenges with long start times, resource occupation, and inefficient data sharing, as containers operate independently and cannot collaborate to complete applications.

Innovation Solution

The method involves determining a first container corresponding to a user request, establishing a link relationship with a logical container, and acquiring a container cluster using a logical address, allowing the first container to call and process tasks with multiple second containers, enabling data sharing and collaborative application handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Docker containers are used to achieve isolation of user private data, then data security and isolation are improved, but containers become fully isolated and cannot share data or work together to complete applications

Engineering Contradiction:
Improvedata securityVSAvoiddata sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a namespace as an intermediary layer between containers. This namespace acts as a mediator that allows containers to access shared data resources while maintaining their isolation. The namespace provides a unified file system view that enables data sharing without breaking container isolation boundaries, thus resolving the contradiction between security and sharing capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If virtual machines are used as the smallest unit for scheduling, then application isolation is achieved, but start times are long and system resources are occupied

Engineering Contradiction:
Improveapplication isolationVSAvoidstart time
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent employs container technology which nests multiple isolated application environments within a single operating system instance. This nesting approach allows containers to share the host OS kernel and system resources, eliminating the need for separate virtual machine instances for each application. As a result, container start times are significantly reduced while maintaining application isolation through user space virtualization rather than full hardware virtualization.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Reliability

If Docker containers work independently with full isolation, then user data security is maintained, but multiple containers cannot call each other or share data to complete the same application

Engineering Contradiction:
Improveuser data securityVSAvoidcontainer collaboration
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a shared namespace that provides universal access to data resources for multiple containers simultaneously. This namespace serves multiple functions: it maintains data isolation for security, enables data sharing for collaboration, and provides a unified interface for container communication. The namespace acts as a universal resource manager that reconciles the conflicting requirements of isolation and collaboration.

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

Data Source

PatentUS10902030B2User request processing method and device
Publication Date: 2021.01.26 ALIBABA GROUP HOLDING LTD
  • US10902030B2 patent drawing
  • US10902030B2 patent drawing
  • US10902030B2 patent drawing

AI summary

The present disclosure provides user request processing methods and devices. One exemplary method includes: determining a first container corresponding to a user request after the user request is received; determining a logical container corresponding to the first container by using a preset relationship between the first container and the logical container; acquiring a container cluster corresponding to the logical container by using a logical address corresponding to the logical container, wherein the container cluster includes at least two second containers; and processing the user request by using the second containers. The user request can be simultaneously processed by the first container and the at least two second containers. The first container can call the second containers, so that different containers can share data and handle the same application together. Further, scale-out of second containers in the container cluster can be implemented, thus improving user request processing capability.