Cloud Platform Event Routing for Multi-App Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of software application development, building, and testing across multiple management applications on a cloud-based platform is inefficient due to the need for converting changes from various proprietary formats, leading to a tedious and inefficient process.

Innovation Solution

A cloud-based platform with an endpoint that receives change events from management applications, featuring a change event processor that determines the source application and sends the event to a corresponding handler for processing, allowing for flexible handling of commit, build, and test events, even if the management application lacks a pre-existing handler, with the option for custom modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different software development management applications are used to manage commit, build, and test events, then the platform can support diverse development workflows and tools, but the process of converting committed changes to a usable format becomes tedious and inefficient

Engineering Contradiction:
Improvesupport for multiple management applicationsVSAvoidefficiency of converting changes
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces an integration framework that acts as an intermediary between multiple management applications and the cloud-based platform. This framework includes event handlers that receive events from different management applications, normalize them into a standard format, and forward them to the platform. This mediator layer eliminates the need for manual conversion while maintaining support for diverse tools, thus resolving the contradiction between versatility and productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration framework implements a universal event handling mechanism that can process events from any management application through a standardized interface. The framework includes configurable event handlers that can be adapted to different application formats, allowing a single platform to universally accept events from multiple sources without requiring separate conversion processes for each application, thereby improving productivity while maintaining adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If manual conversion processes are used to implement changes from different management applications, then format compatibility can be achieved, but the process becomes tedious and time-consuming

Engineering Contradiction:
Improveformat compatibilityVSAvoidtime for conversion process
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The integration framework performs preliminary normalization of events at the point of receipt. Event handlers are pre-configured with knowledge of different management application formats and automatically convert incoming events to the standard platform format before processing. This preliminary action ensures format compatibility is achieved automatically without requiring time-consuming manual conversion later in the process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service conversion through automated event handlers that independently process and normalize events from different management applications. The framework automatically detects the source application, selects the appropriate conversion rules, and transforms the event format without human intervention. This self-service mechanism maintains reliable format compatibility while eliminating time loss associated with manual conversion processes.

Inventive Principle:
Principle #25Self-service

3Productivity

If a single integrated platform is implemented to manage all development, building, and testing, then process efficiency can be improved, but the complexity of integrating multiple management applications increases

Engineering Contradiction:
Improveoverall process efficiencyVSAvoidintegration framework complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The integration framework is segmented into independent, modular event handlers, each responsible for processing events from specific management applications or event types. This segmentation allows the system to manage complexity by dividing the integration task into smaller, manageable units that can be configured and maintained independently, thereby enabling a single integrated platform to improve productivity without becoming unmanageably complex.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The integration framework implements dynamic event routing and handler selection based on the incoming event source and type. The system can dynamically load, configure, and unload event handlers as needed, allowing the platform to adapt to different management applications without requiring a fixed, complex integration structure. This dynamic approach maintains high process efficiency while managing integration complexity through flexible, on-demand configuration.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10795669B2Systems and methods for integrating software source control, building, and testing applications
Publication Date: 2020.10.06 SERVICENOW INC
  • US10795669B2 patent drawing
  • US10795669B2 patent drawing
  • US10795669B2 patent drawing

AI summary

Systems and methods are disclosed that provide a cloud-based platform having an endpoint that receives a change event to a software application hosted by a virtual server from a management application. The change event includes a commit event, build event, or test event implemented on the software application. The management application manages commit events, build events, or test events implemented on the software application. The platform includes a change event processor that determines that the change event was generated by the management application and sends the change event to a handler based on the management application. The platform also includes the handler of a set of handlers that processes the change event based on the management application to update the software application. Each handler of the set of handlers corresponds to a respective management application and is configured to process a respective change event generated by the respective management application.