Event Processing Compiler for Rapid Code Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for developing event processing language code are inefficient, as they require lengthy compilation and deployment processes, lack effective debugging tools, and struggle to maintain consistency between development and production environments, leading to significant time losses and limited understanding of internal occurrences during output generation.

Innovation Solution

The implementation of an event processing compiler that transforms event processing language code into development environment script language code, providing features like syntax and error highlighting, intelligent code completion, and debugging functionalities, ensuring that queries yield identical results in both development and production environments by accommodating event processing attributes such as temporal data handling and streaming inputs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional compilation and deployment processes are used for event processing language code, then the code can be executed in production environments, but the development process becomes lengthy and inefficient

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidcompilation and deployment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces an event processing compiler as an intermediary tool that transforms event processing language code into executable code. This compiler provides syntax highlighting, error detection, and code completion features during development, enabling rapid iteration without lengthy compilation cycles. The compiler acts as a mediator between the developer and the production environment, allowing efficient development while maintaining execution compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If conventional development methods are used without specialized debugging tools, then the development process is simpler, but debugging capabilities are insufficient and understanding of internal occurrences is limited

Engineering Contradiction:
Improvedebugging capabilityVSAvoiddevelopment environment complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The event processing compiler provides self-service debugging capabilities by automatically detecting syntax errors, providing code completion suggestions, and highlighting issues in the event processing language code. The system serves itself by incorporating built-in validation and error detection mechanisms that eliminate the need for external debugging tools, thereby enhancing debugging capability without proportionally increasing environment complexity.

Inventive Principle:
Principle #25Self-service

3Reliability

If conventional development environments are used, then the setup is simpler, but consistency between development and production environments cannot be maintained

Engineering Contradiction:
Improveenvironment consistencyVSAvoidcompiler implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements equipotentiality by ensuring that the event processing compiler operates identically in both development and production environments. The same compilation rules, syntax validation, and error detection mechanisms are applied universally, eliminating environment-specific behaviors. This ensures that code compiled in the development environment will execute consistently in the production environment, maintaining reliability without requiring complex environment management.

Inventive Principle:
Principle #12Equipotentiality

4Productivity

If rapid development and testing are implemented, then productivity improves, but ensuring consistent output across environments becomes more challenging

Engineering Contradiction:
Improvedevelopment speedVSAvoidoutput consistency
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The event processing compiler performs preliminary validation and error detection during the development phase, identifying and flagging potential issues before code deployment. By pre-checking syntax, semantics, and logical consistency in the development environment, the system ensures that only validated code progresses to production. This preliminary action maintains output consistency across environments while enabling rapid development iteration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9952915B2Event processing development environment
Publication Date: 2018.04.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9952915B2 patent drawing
  • US9952915B2 patent drawing
  • US9952915B2 patent drawing

AI summary

Embodiments described herein are directed to methods, and systems for generating event processing language code in a development environment using an event processing compiler. A query in event processing language is received in a development environment. The query can be associated with sample data from input files or an input data source. An event processing compiler compiles the query, where the compiler transforms the query from event processing language code to a development environment script language code. In particular, the event processing language code transforms the code based on event processing attributes that are intricately aligned in syntax and semantic between the event processing language and the development environment script language. The query as a development environment script is executed using sample data. Executing the query generates output comprising final results data, intermediate results data, and provides for display warnings when mismatches exist between the results data and output specifications.