# US 2022/0036206 A1 · Containerized distributed rules engine

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0036206 A1
- Document ID: US20220036206A1
- Status: Published application
- Kind: A1
- Application number: 17/005,223
- Filed: 2020-08-27
- Published: 2022-02-03
- Earliest claimed: 2020-07-29
- Assignees: Red Hat, Inc.
- Applicants: Red Hat, Inc.
- Inventors: Edoardo Vacchi; Daniele Zonca
- Web page: https://patentgrep.com/patent/US20220036206A1

## CPC

- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06N 5/025: Extracting rules from data
- G06F 8/61: Installation
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5061: {Partitioning or combining of resources}
- G06F 9/544: {Buffers; Shared memory; Pipes}
- G06F 2009/45562: {Creating, deleting, cloning virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

A method includes generating a rule unit as a containerized microservice on a cloud platform. The method further includes deploying, by a processing device, the containerized microservice on a container platform. The method further includes enabling message passing between the containerized microservice and additional containerized microservices over a shared channel.

## Claims

### Claim 1

A method, comprising:
generating a rule unit as a containerized microservice on a cloud platform;
deploying, by a processing device, the containerized microservice on a container platform; and
enabling message passing between the containerized microservice and additional containerized microservices over a shared channel.

### Claim 2 (depends on 1)

The method of claim 1, wherein generating the rule unit as the containerized microservice comprises:
identifying the rule unit in a manifest file;
generating a rule unit microservice comprising one or more rules of the manifest file; and
packaging the rule unit microservice into a rule unit container as a containerized microservice.

### Claim 3 (depends on 2)

The method of claim 2, further comprising generating the one or more rules of the manifest file in an executable format.

### Claim 4 (depends on 3)

The method of claim 3, wherein the executable format provides read and write access to a data source corresponding to the rule via an application programming interface (API).

### Claim 5 (depends on 4)

The method of claim 4, wherein the API is a representational state transfer (REST) API.

### Claim 6 (depends on 2)

The method of claim 2, wherein deploying the containerized microservice on the container platform comprises:
associating, from the manifest file, a data source of the containerized microservice to a corresponding backing channel; and
initializing a container platform scheduler to schedule the containerized microservice for execution.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
identifying a fact in a queue associated with the containerized microservice;
storing the fact in a local working memory associated with the containerized microservice;
executing the containerized microservice;
updating the fact in the local working memory in view of the executing; and
propagating updated fact to the one or more additional containerized microservices via the shared channel.

### Claim 8

A system, comprising:
a local memory; and
a processing device operatively coupled to the memory, the processing device to:
generate a rule unit as a containerized microservice on a cloud platform;
deploy the containerized microservice on a container platform; and
enable message passing between the containerized microservice and additional containerized microservices over a shared channel.

### Claim 9 (depends on 8)

The system of claim 8, wherein to generate the rule unit as the containerized microservice the processing device is to:
identify the rule unit in a manifest file;
generate a rule unit microservice comprising one or more rules of the manifest file; and
package the rule unit microservice into a rule unit container as a containerized microservice.

### Claim 10 (depends on 9)

The system of claim 9, the processing device further to generate the one or more rules of the manifest file in an executable format.

### Claim 11 (depends on 10)

The system of claim 10, wherein the executable format provides read and write access to a data source corresponding to the rule via an application programming interface (API).

### Claim 12 (depends on 11)

The system of claim 11, wherein the API is a representational state transfer (REST) API.

### Claim 13 (depends on 9)

The system of claim 9, wherein to deploy the containerized microservice on the container platform the processing device is to:
associate, from the manifest file, a data source of the containerized microservice to a corresponding backing channel; and
initialize a container platform scheduler to schedule the containerized microservice for execution.

### Claim 14 (depends on 13)

The system of claim 13, the processing device further to:
identify a fact in a queue associated with the containerized microservice;
store the fact in the local memory associated with the containerized microservice;
execute the containerized microservice;
update the fact in the local memory in view of the executing; and
propagate the updated fact to the one or more additional containerized microservices via the shared channel.

### Claim 15

A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause the processing device to:
generate a rule unit as a containerized microservice on a cloud platform;
deploy the containerized microservice on a container platform; and
enable, by the processing device, message passing between the containerized microservice and additional containerized microservices over a shared channel.

### Claim 16 (depends on 15)

The non-transitory computer-readable storage medium of claim 15, wherein to generate the rule unit as the containerized microservice the processing device is to:
identify the rule unit in a manifest file;
generate a rule unit microservice comprising one or more rules of the manifest file; and
package the rule unit microservice into a rule unit container as a containerized microservice.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, the processing device further to generate the one or more rules of the manifest file in an executable format.

### Claim 18 (depends on 17)

The non-transitory computer-readable storage medium of claim 17, wherein the executable format provides read and write access to a data source corresponding to the rule via an application programming interface (API).

### Claim 19 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein to deploy the containerized microservice on the container platform the processing device is to:
associate, from the manifest file, a data source of the containerized microservice to a corresponding backing channel; and
initialize a container platform scheduler to schedule the containerized microservice for execution.

### Claim 20 (depends on 19)

The non-transitory computer-readable storage medium of claim 19, the processing device further to:
identify a fact in a queue associated with the containerized microservice;
store the fact in a local memory associated with the containerized microservice;
execute the containerized microservice;
update the fact in the local memory in view of the executing; and
propagate the updated fact to the one or more additional containerized microservices via the shared channel.
