Microservice Build Knowledge Capture for Linux Tool Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Linux-based IT tools for microservice applications are not always compatible and require extensive manual knowledge acquisition, leading to time-intensive and error-prone processes due to numerous versions and customization options.
Innovation Solution
A system and method that automatically captures and provides computerized knowledge by analyzing raw build data, using large language models and natural language processing to extract and store configuration settings, tool versions, and compatibility information in a knowledge base, enabling automated build pipeline generation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual knowledge acquisition by experts is used, then comprehensive knowledge about tool compatibility and configuration can be obtained, but the process becomes time-intensive and error-prone
Solution Approach 1:
The system performs self-service by automatically capturing build data from development projects and generating knowledge about tool compatibility and configuration settings without requiring expert intervention. The build systems themselves provide the data needed to create the knowledge base, eliminating the need for manual expert analysis while maintaining high accuracy through real-world validation.
Solution Approach 2:
The patent replaces the mechanical process of manual expert knowledge acquisition with an automated computerized system. Instead of experts manually researching and documenting tool compatibility, the system automatically collects build data, analyzes it using processors, and generates knowledge artifacts, substituting human cognitive work with computational processes.
2Adaptability or versatility
If comprehensive manual knowledge about all tools and versions is acquired, then suitable tool selections can be made, but the complexity of managing this knowledge increases
Solution Approach 1:
The system segments the comprehensive knowledge about tools and configurations into individual knowledge artifacts derived from specific build data. Each build result generates discrete knowledge entries about particular tool combinations and configuration settings, allowing the knowledge to be organized in manageable units that can be independently stored, retrieved, and updated without managing the entire knowledge base as a single complex entity.
Solution Approach 2:
The patent adds a new dimension to knowledge management by organizing knowledge along the dimension of build results and configuration parameters. Instead of managing knowledge solely by tool names, the system structures knowledge around build data dimensions including configuration settings, tool versions, and validation results, creating a multi-dimensional knowledge space that simplifies retrieval and reduces management complexity.
3Reliability
If frequent updates to tool landscape knowledge are performed manually, then current best practices are maintained, but the time and effort required increases significantly
Solution Approach 1:
The system enables continuous knowledge updates by automatically capturing build data from ongoing development projects. As builds continue to execute with various tool configurations, the system continuously accumulates new knowledge artifacts, maintaining current best practices without requiring periodic manual intervention. The useful action of knowledge acquisition becomes continuous rather than periodic.
Solution Approach 2:
The system implements feedback loops where build results automatically feed back into the knowledge base. Each build execution provides feedback about tool compatibility and configuration effectiveness, which is automatically processed and used to update knowledge artifacts. This closed-loop feedback mechanism ensures knowledge remains current while eliminating the manual effort previously required for updates.
4Adaptability or versatility
If extensive configuration options and versions are supported, then flexibility in tool selection is improved, but the difficulty of detecting and measuring compatibility increases
Solution Approach 1:
The system performs preliminary action by capturing and validating configuration data before builds execute. Build systems are configured with specific tool versions and settings in advance, and the automatic capture process validates these configurations prior to execution. This preliminary validation simplifies compatibility detection by establishing known-good configurations before they are tested in actual builds.
Solution Approach 2:
The patent uses copying to create knowledge artifacts that replicate successful configuration patterns from actual builds. Instead of manually analyzing and documenting compatibility relationships, the system copies the exact configuration data and tool settings from working builds into the knowledge base. This copying approach automatically preserves compatibility information without requiring manual verification of complex configuration relationships.
Data Source
AI summary
Computer-implemented method and corresponding system for capturing and providing knowledge to be used in a Linux-based IT tool environment for developping micro service applications The present invention relates to a system (S) for capturing and providing knowledge to be used in a Linux-based IT tool environment for developping micro service applications, comprising: - an interface (IF) connected with at least one data gathering unit which receives raw build data as configuration patterns found in the Internet and/or in accessible repositories and which receives development data of IT based development projects comprising project requirements and configuration data including their build results expressing if a run of a piece of configuration data fullfils the requirements or not, - an extracting unit (E) which is configured to extract knowledge to be used in a Linux-based IT tool environment for developping micro service applications from the raw build and development data and form the knowledge in a computerized permanently storable format and which is configured to store such formed knowledge in a connectable storage (KB) whereby such knowledge comprises version and configuration settings, and - an access interface (AC) accessible from outside (OUT) of the system whereby the interface is configured to output at least parts of the formed knowledge to the outside of the system.