Messaging Kernel for Asynchronous Enterprise Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging systems, such as JMS, lack a robust and flexible foundation for asynchronous messaging that supports multiple standards, advanced features, and maintains message order, reliability, availability, security, and performance in modern enterprise transaction processing.
Innovation Solution
A messaging kernel that provides basic messaging features like point-to-point and publish/subscribe messaging, persistent and non-persistent messages, acknowledgement modes, quotas, statistics, message sorting, and message paging, while being agnostic of JMS and J2EE specifications, and supporting higher-level message-oriented middleware systems like JMS and WS-RM.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a messaging system supports multiple standards and advanced features, then the system's adaptability and functionality are improved, but the system's complexity increases
Solution Approach 1:
The messaging system is divided into distinct layers: a standardized messaging kernel at the bottom that handles core messaging functions, and multiple protocol adapters (JMS, WS-RM, etc.) at the top that implement different standards. This segmentation allows the system to support multiple standards without increasing the complexity of the core messaging engine, as each standard is implemented as a separate adapter layer.
Solution Approach 2:
The messaging kernel acts as an intermediary layer between the messaging applications and the various transport protocols. It provides a unified interface for message production and consumption while handling protocol-specific details through adapter components. This mediator approach allows the system to support multiple standards without requiring each standard to be integrated directly into the core system.
2Reliability
If message ordering and sequencing are maintained, then message reliability is improved, but processing time and system performance may be degraded
Solution Approach 1:
Sequence numbers are assigned to messages at the time of message creation or insertion into the queue, before any processing or delivery occurs. This preliminary assignment of sequence numbers allows the system to maintain message ordering without requiring complex real-time coordination during message processing, thereby reducing processing time while ensuring reliability.
3Adaptability or versatility
If advanced messaging features are implemented, then the system's functionality is improved, but the ease of operation and implementation becomes more difficult
Solution Approach 1:
The messaging kernel implements a universal set of messaging primitives and interfaces that can be used across all messaging scenarios and standards. This universal interface design allows advanced features to be implemented once at the kernel level and automatically available to all protocol adapters, making the system easier to implement and maintain while providing extensive functionality.
Data Source
AI summary
The present invention enables a messaging kernel to serve as the basis for asynchronous messaging in a Web service platform. The kernel provides basic messaging features, including point-to-point and publish/subscribe messaging, persistent and non-persistent messages, a variety of acknowledgement modes, two-phase commit transactions, quotas, statistics, message sorting, and message paging. It also includes some novel features that maintain message order based on application requirements. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.