Cloud Event Server Subscription and Notification Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud computing systems face inefficiencies in tracking, logging, and parsing events related to virtual machines, which are ephemeral and require extensive manual effort, lacking a systematic approach to event notification and data management.

Innovation Solution

An event server is configured to detect and log events in a cloud environment, allowing applications to subscribe to specific events, and providing event data to identified applications, with a modular structure including detection, subscription, and notification modules to manage and distribute event data efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If manual tracking and logging of virtual machine events is performed, then event data can be captured, but extensive time and manual effort are required

Engineering Contradiction:
Improveevent data captureVSAvoidmanual effort time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system enables self-service event notification where the event server automatically detects events, logs event data, and notifies subscribed applications without requiring manual intervention. The event server autonomously examines subscription data to identify which applications should receive which events, eliminating the need for manual tracking and logging efforts

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The event server acts as an intermediary component between virtual machine operations and applications. It receives event data from the cloud environment, processes and logs the data, then distributes notifications to appropriate applications based on subscription data, automating the entire event management workflow

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If virtual machines are made ephemeral for cloud flexibility, then resource scaling and mobility improve, but event tracking and state persistence become more difficult

Engineering Contradiction:
Improvecloud flexibilityVSAvoidevent tracking reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system establishes event subscription mechanisms in advance before virtual machines are created or destroyed. Applications subscribe to specific event types ahead of time, and the event server maintains subscription data that persists independently of virtual machine lifecycle. When events occur, the server automatically notifies subscribed applications, ensuring reliable event tracking regardless of virtual machine ephemeral nature

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The event server provides universal event notification services that work across different virtual machine configurations, cloud environments, and application types. The standardized event data format and subscription mechanism allow the same system to handle diverse events from various ephemeral virtual machines, making the solution universally applicable while maintaining reliability

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

Data Source

PatentUS10684897B2Event notification
Publication Date: 2020.06.16 RED HAT INC
  • US10684897B2 patent drawing
  • US10684897B2 patent drawing
  • US10684897B2 patent drawing

AI summary

A server computer determines that an application of a plurality of applications in a cloud subscribes to an event with respect to a plurality of attributes of event data. The server computer, responsive to determining that at least one of the plurality of attributes has changed, executes the application workflow and sends a notification to the application, the notification indicating that at least one of the plurality of attributes has changed.