Runtime ESP Container Image Generation via Component Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in efficiently creating and managing Event Stream Processing (ESP) project container images, leading to inefficiencies in data streaming and processing.
Innovation Solution
A system and method for creating an ESP project container image by generating a manifest file, executing container file generator and build kit software, and identifying required software components to generate a subset container file, ultimately creating the ESP project container image for data streaming and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional container image creation methods are used for ESP projects, then the container image can be created, but the process is inefficient and causes interruptions in data streaming
Solution Approach 1:
The patent applies preliminary action by creating container images offline before data streaming begins. The build kit executes build instructions to generate container images in advance, storing them in image repositories. This allows the ESP system to use pre-built images during runtime without interrupting data streaming operations, thus resolving the contradiction between creation efficiency and streaming continuity.
2Reliability
If complete software components are included in container images, then the ESP project can execute properly, but the container image size increases and creation time increases
Solution Approach 1:
The patent applies extraction by separating build-time software components from runtime software components. The build kit identifies and extracts only the necessary runtime components needed for ESP execution, excluding build-time tools and complete software suites. This creates smaller, faster-to-build container images while maintaining execution capability through dynamic component loading from the host system.
Solution Approach 2:
The patent segments the container image into two parts: a minimal base image containing only runtime dependencies, and separate build-time components that remain on the host system. This segmentation allows the container image to be created quickly with essential components only, while still supporting full ESP project execution by leveraging host system resources for build-time operations.
3Adaptability or versatility
If container images are created with all necessary software components, then the ESP project can run independently, but the device complexity and storage requirements increase
Solution Approach 1:
The patent applies universality by creating a shared build environment that serves multiple ESP projects. The host system maintains a build kit and build instructions that can generate container images for different projects, reducing the need for each project to include its own complete build toolchain. This multi-functional approach reduces device complexity while maintaining project independence through standardized build processes.
Data Source
AI summary
A system and method include creating a project package for an Event Stream Processing (ESP) project, generating a first manifest file from the project package, creating a first container pod on a cluster based on the first manifest file, executing a container file generator software and a build kit software on the first container pod, executing an ESP server on the container file generator software, executing the ESP project on the ESP server such that data is not streaming to the ESP server, identifying a list of required software components needed to execute the ESP project, creating a container file having a subset of software components based on the list of required software components, generating a ESP project container image for the ESP server based on the container file, and deploying the ESP project using the ESP project container image to analyze data streamed to the ESP project.