Centralized Event Broker for CI/CD Pipeline Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of communication and central reporting among specialized plug-ins in software development and CI/CD pipelines hinders comprehensive lifecycle management, leading to inefficiencies and difficulties in integrating new plug-ins.

Innovation Solution

A system for centralized application development and pipeline management via event data streaming, which receives event data from discrete components, analyzes it for conformity to a standardized data structure, and generates update signals for real-time monitoring and display on a graphical dashboard.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If specialized plug-ins are used in software development pipelines, then functionality and capabilities are improved, but communication and integration among plug-ins become more difficult

Engineering Contradiction:
ImprovefunctionalityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event broker as an intermediary component that receives events from multiple specialized plug-ins and distributes them to appropriate subscribers. This mediator layer enables communication between plug-ins without requiring direct integration between them, thus maintaining functionality while reducing integration complexity. The event broker standardizes event formats and routing, allowing diverse plug-ins to interact through a common interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple discrete components operate independently in the pipeline, then flexibility and modularity are improved, but centralized monitoring and reporting become more difficult

Engineering Contradiction:
ImprovemodularityVSAvoidpipeline visibility
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where discrete pipeline components publish events about their state and operations to a centralized event broker. These events are then aggregated and made visible through a unified dashboard interface, providing comprehensive pipeline visibility. The feedback loop allows independent components to contribute information to a centralized view without sacrificing their autonomy, enabling both modularity and centralized monitoring.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If manual input is required for pipeline management, then flexibility in handling complex scenarios is improved, but time consumption and efficiency are worsened

Engineering Contradiction:
ImproveflexibilityVSAvoidtime consumption
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements automated event routing and pipeline orchestration that performs preliminary actions based on predefined rules and event patterns. When events are published to the event broker, the system automatically routes them to appropriate handlers and triggers subsequent pipeline actions without requiring manual intervention. This preliminary automation handles routine scenarios efficiently while preserving the ability to handle complex cases, reducing time consumption while maintaining operational flexibility.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250165249A1System and method for centralized application development and pipeline management via event data streaming
Publication Date: 2025.05.22 BANK OF AMERICA CORP
  • US20250165249A1 patent drawing
  • US20250165249A1 patent drawing
  • US20250165249A1 patent drawing

AI summary

Systems, computer program products, and methods are described herein for centralized application development and pipeline management via event data streaming. The present disclosure embraces event data received from discrete components of an application development pipeline platform. The event data is received directly, via webhooks, or via change data capture. The event data is analyzed to determine conformity to a standardized data structure. If the discrete components already transmit and receive event data in the standardized data structure, the application development pipeline platform communicates with such discrete components directly. If the discrete components don't transmit and receive event data in the standardized data, a middleware layer receives the event data from the discrete components and transforms the event data from the discrete components to the standardized data structure.