Backward Chaining Rule Engine for Container Cluster Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In containerized computing clusters, manually encoding business logic using procedural programming languages is tedious, error-prone, and inefficient for collaboration, especially when encoding rules for managing stateful applications.

Innovation Solution

Implementing a rule engine with backward chaining functionality to infer missing configuration information and trigger corrective actions automatically, utilizing a rule engine that evaluates rules against facts to determine criteria for cluster configurations and perform necessary actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If manual encoding of business logic using procedural programming languages is used, then implementation is straightforward, but it is tedious, error-prone, and inefficient for collaboration

Engineering Contradiction:
Improveease of implementationVSAvoidcollaboration efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent introduces a rule engine as an intermediary layer between the container orchestration system and business logic requirements. This rule engine uses Domain Specific Language (DSL) to encode rules, serving as a mediator that translates high-level business requirements into executable logic, thereby improving collaboration efficiency while maintaining ease of implementation through standardized rule templates

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter of rule encoding from procedural programming languages to Domain Specific Language (DSL). This parameter change enables more efficient collaboration by allowing rules to be defined in a domain-specific syntax that is more intuitive and easier to collaborate on, while the rule engine handles the complexity of interpretation and execution

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If traditional rule evaluation methods are used, then implementation is simple, but they require significant computational resources and time for forward chaining through all rules

Engineering Contradiction:
Improveimplementation complexityVSAvoidcomputational resource usage
Core Design Contradiction:
Device complexityVSUse of energy by moving object

Solution Approach 1:

The patent inverts the traditional forward chaining approach by implementing backward chaining. Instead of starting from rules and evaluating them against facts to find conclusions, the system starts from a goal state and works backward to determine what facts and rules are needed to achieve it. This inversion dramatically reduces computational resources by only evaluating relevant rules rather than all rules in the system

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The system extracts only the necessary rules and facts required to achieve the goal state, rather than processing the entire rule set. By taking out only the relevant subset of rules that contribute to the goal, the backward chaining approach minimizes computational resource usage while maintaining implementation simplicity

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If comprehensive rule evaluation is performed to ensure accuracy, then inference precision is high, but processing time increases significantly

Engineering Contradiction:
Improveinference accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-processing and organizing rules and facts into structures that facilitate efficient backward chaining. Rules are pre-compiled and indexed, and the system pre-identifies relevant rule subsets based on goal characteristics. This preliminary preparation enables accurate inference without the time penalty of comprehensive real-time evaluation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240144048A1Using rule engine with backward chaining in a containerized computing cluster
Publication Date: 2024.05.02 RED HAT INC
  • US20240144048A1 patent drawing
  • US20240144048A1 patent drawing
  • US20240144048A1 patent drawing

AI summary

A method includes determining, by a processing device, a criterion associated with a configuration of a containerized computing cluster, wherein the containerized computing cluster comprises a plurality of virtualized computing environments running on one or more host computer systems; evaluating a rule against a fact, wherein the rule specifies a condition including the criterion and an action to perform if the condition of the rule is satisfied; and responsive to determining that the condition specified by the rule matches the asserted fact, performing the action specified by the rule, wherein the action comprises a notification regarding the configuration of the containerized computing cluster.