Stream Analytics Custom Component Registration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users of Stream Analytics Platforms face inefficiencies and errors when reconfiguring custom logic across different distributed processing pipelines, requiring repetitive steps to upload and configure custom components, which is time-consuming and prone to mistakes.

Innovation Solution

A system and method for registering custom components on a Stream Analytics Platform, allowing users to receive, parse, and register program files and instructions, making the custom components available on the GUI for designing distributed processing pipelines, enabling primary and secondary users to utilize them without repetitive configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users manually upload and configure custom components for each distributed processing pipeline, then custom logic can be executed on each pipeline, but the process becomes repetitive and time-consuming

Engineering Contradiction:

Improvecustom logic execution capabilityVSAvoidconfiguration time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically extracting program code from uploaded program files and pre-configuring custom components before the user needs to use them. The extraction module parses program files to obtain executable code, and the component configuration module pre-configures custom components with this extracted code, so when users create new pipelines, the components are already ready for use without manual reconfiguration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements copying by storing extracted program code and custom component configurations in a repository that can be reused across multiple distributed processing pipelines. Instead of re-uploading and re-configuring the same custom logic for each pipeline, users can copy previously configured custom components from the repository and apply them to new pipelines, significantly reducing repetitive configuration work.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If users manually re-configure custom components on new pipelines, then custom logic can be executed, but errors may occur during reconfiguration

Engineering Contradiction:

Improvecustom logic execution capabilityVSAvoidconfiguration accuracy

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements self-service by enabling custom components to automatically extract their own program code from uploaded program files and configure themselves without manual user intervention. The extraction module automatically parses program files to obtain executable code, and the component configuration module automatically configures custom components with this extracted code and metadata, eliminating manual configuration steps that could introduce errors and improving configuration accuracy.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If the system supports custom components for distributed processing, then custom logic can be executed, but the configuration process becomes complex and onerous

Engineering Contradiction:

Improvecustom logic execution capabilityVSAvoidconfiguration process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies extraction by separating the program code extraction process from the custom component configuration process. The extraction module specifically extracts executable program code from uploaded program files, while the component configuration module handles the configuration of custom components with this extracted code. This separation simplifies the overall configuration process by breaking it into manageable, automated steps, reducing the complexity users would otherwise face.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary mechanism in the form of a component repository that mediates between program file uploads and custom component deployment. The extraction module extracts code and stores it in the repository, the configuration module retrieves and configures components from the repository, and users can access pre-configured components from the repository when creating pipelines. This intermediary repository simplifies the interaction between users and the complex configuration process.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10031747B2System and method for registration of a custom component in a distributed computing pipeline

Publication Date: 2018.07.24 GATHR DATA INC

AI summary

The present disclosure relates to system(s) and method(s) for registration of a custom component on a Stream Analytics Platform. The system is configured to receive a program file and one or more registration instructions corresponding to the custom component, from a primary user of the Stream Analytics Platform. Further, a program code may be extracted from the program file by parsing the program file. Further, the system is configured to register the program code as a registered custom component, on the Stream Analytics Platform based on the one or more registration instructions. Once registered, the registered custom component is available over a Graphical User Interface (GUI) of the Stream Analytics Platform. The system enables at least the primary user or a set of secondary users of the Stream Analytics platform to use the registered custom component, based on the one or more registration instructions, for designing a distributed processing pipeline.