Event Message Pulling Module for Filtered Cloud Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in securely and efficiently transmitting protected data between multiple cloud-based domains with proprietary communication protocols, and there is a need for a solution that transcends the limitations of local servers.
Innovation Solution
A module for pulling event messages to a cloud-based data service application that applies filter criteria and schema validation, enabling secure and efficient message transfer between different cloud-based domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If cloud-based implementations are used to remove reliance on local servers, then scalability and maintenance overhead are improved, but security vulnerabilities and data protection compliance become worsened
Solution Approach 1:
The patent introduces a message broker as an intermediary component between data streaming applications and data service applications. This broker implements schema validation, filtering, and routing mechanisms that ensure secure data transmission while maintaining cloud-based scalability. The broker acts as a trusted mediator that enforces security policies without requiring changes to the underlying cloud infrastructure.
Solution Approach 2:
The system performs schema validation and filtering operations before data is transmitted between cloud domains. By validating messages against predefined schemas and applying filters in advance, the system ensures data protection compliance and security requirements are met before data enters the cloud transmission pipeline, preventing security vulnerabilities from arising.
2Adaptability or versatility
If multiple cloud-based domains with proprietary communication protocols are connected, then data service capability is improved, but communication compatibility becomes worsened
Solution Approach 1:
The message broker is designed with universal messaging capabilities that can handle multiple proprietary communication protocols simultaneously. It implements a standardized internal message format and protocol conversion mechanisms, allowing it to communicate with different cloud domains using their respective protocols while maintaining consistent data validation and routing rules across all domains.
Solution Approach 2:
The broker serves as a protocol translation layer between domains with different communication protocols. It receives messages from various protocols, normalizes them to an internal format, applies validation and filtering, then converts them to the appropriate protocol for the destination domain, thereby resolving compatibility issues without limiting service capability.
3Adaptability or versatility
If event messages are transmitted between multiple cloud domains, then message routing flexibility is improved, but bandwidth consumption becomes worsened
Solution Approach 1:
The system extracts and applies filtering rules to messages before transmission. By evaluating filter criteria and routing rules in advance within the broker, only necessary messages are transmitted to specific destinations. This prevents unnecessary bandwidth consumption by filtering out irrelevant messages and routing only those that match specific criteria to the appropriate cloud domains.
Solution Approach 2:
The broker performs routing decisions and message filtering before data transmission occurs. By determining the destination and applying filters in advance, the system avoids unnecessary data transmission across the cloud network, thereby reducing bandwidth consumption while maintaining flexible routing capabilities based on message content and destination requirements.
Data Source
AI summary
A module for pulling an event message to a cloud-based data service application is provided. The module may be configured to pull at least one event message from at least one cloud-based data streaming application. For each event message of the at least one event message, the module may be configured to select and retrieve at least one filter criterion from a plurality of filter criteria based at least in part on at least one event message configuration parameter of the event message. The module may be configured to apply the at least one filter criterion to the event message. If the event message passes the filter criterion, the module may be configured to determine whether event message schema validation is required based on the at least one event message configuration parameter, among other things.