Red Hat, Inc.

Edoardo Vacchi

Paolo Antinori

Ricardo Zanini Fernandes

Tiago Dolphine

Systems and methods for uniform addressing can include receiving a request to execute a component of an application and assigning a component identifier to the component of the application. It could also include determining a component type identifier of the component and responsive to a determination that the component is instantiated, assigning a component instance identifier to an instance of the component. It could further include invoking the component by a global address comprising the component type identifier and at least or of the component identifier and component instance identifier.

Uniform addressing in business process engine

A rules engine that is running a rules-based application executing on a computing device comprising a processor device receives a first transaction that includes a plurality of data fields, at least some of the data fields including data to be evaluated by a plurality of rules identified in the rules-based application, the first transaction including encrypted data in a first encrypted data field of the plurality of data fields that has been encrypted with a symmetric key in accordance with a structured encrypted algorithm. The rules engine queries the encrypted data using a first query token generated using the symmetric key to determine if the encrypted data includes a value used in a first condition identified in the plurality of rules. The rules engine takes an action based at least in part on querying the encrypted data.

Structured encryption rules engine

In various examples disclosed herein, provided is a method and system for cross-validating files to facilitate code generation. The system can perform the cross-validation in phases of disparate files to enable the interoperability of the files. The files can include representations of tasks that are organized differently and differ in format and semantics. The method and system described herein can perform syntax and semantic validation on the files to check for errors, and then identify terms and names identified in the tasks associated with the files along with signatures (e.g., schemas for data models or function signatures for function invocations) associated with the names. After error checking is complete, and after the names and signatures are identified, the names and signatures in the respective files can be cross-validated to find matching tasks, and code is generated that utilizes the cross-validated and matching tasks.

Cross-validating files to facilitate code generation

In various examples disclosed herein, provided is a method for mapping data models to facilitate code generation. The method can include receiving a first file comprising a first data model of a first group of components and a second file comprising a second data model of a second group of components. The method can also include converting the first data model into a first intermediate data model. The method can also include converting the second data model into a second intermediate data model. The method can also include mapping the first intermediate data model to the second intermediate data model to generate a map of matching elements. The method can also include generating code to be executed based at least in part on the map of matching elements.

Mapping data models to facilitate code generation

In various examples disclosed herein, provided is a method for segmenting processes into stand-alone services. The method can include receiving a file that includes information relating to a plurality of components. The method can also include determining a first resource cost associated with deploying each component in a respective service and a second resource cost associated with deploying each component in a single service. The method can also include determining a segmentation plan that segments the plurality of components into groups of one or more components that can be executed by respective services, where a third resource cost associated with the segmentation plan is lower than the first resource cost and the second resource cost. The method can also include generating instructions to deploy the respective services on the one or more computing devices.

Segmenting processes into stand-alone services

Removing inactive components to facilitate code generation. A first file that includes a first group of components in a first notation syntax and a second file that includes a second group of components in a second notation syntax is received. A first set of inactive components of the first group of components is identified. A second set of inactive components of the second group of components is identified. The components of the first group of components and the second group of components that are not marked as inactive components are active components. Code to be executed based on the active components is generated.

Removing inactive code to facilitate code generation

In various examples disclosed herein, provided is a method for generating metadata to facilitate code generation. The method can include receiving a first file that includes information relating to a first set of components in a first notation syntax and a second file that includes information relating to a second set of components in a second notation syntax. The method can also include cross-validating the first file and the second file to determine that a first reference, in a first component of the first set of components, to a second component of the second set of components is valid. The method can also include generating a first metadata file that includes identification information relating to the first reference. The method can also include generating code to be executed based on the first metadata file, the first file, and the second file.

Generating metadata to facilitate code generation

A method of performing resource discovery includes receiving, by a processing device, a resource identifier describing a resource of a computing cluster to be accessed by a workflow application. The method also includes sending the resource identifier to a container orchestration API to determine whether an endpoint exists for the resource. The method also includes, in response to an indication from the container orchestration API that the endpoint exists, receiving, from the container orchestration API, endpoint details used to access the resource, identifying an endpoint address based on the endpoint details, and binding the endpoint address to the resource in a runtime version of the workflow application to enable the workflow application to access the resource.

Growing community of inventors

Milan, Italy

Edoardo Vacchi