Web Services Runtime Framework Stateless Messaging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Web services message processing runtime frameworks face inefficiencies due to state-full protocols, reliance on mapping registries, and indirect communication between protocols and the runtime object, which hampers scalability and performance, especially in handling diverse business models requiring reliability and security features.
Innovation Solution
The improved runtime framework eliminates mapping registries, adopts state-less protocols, and enables direct communication between protocols and the runtime object, incorporating message key-to-endpoint method mapping into Web service data and supporting hibernation for efficient processing of messages across different protocols like WS-Reliable Messaging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state-full protocols are used in Web services message processing, then reliability features can be maintained, but memory consumption increases and scalability deteriorates
Solution Approach 1:
The protocol processing is segmented into state-less protocol handlers that process messages independently without maintaining internal state between messages. Each protocol handler operates autonomously, processing only the current message context provided in the message itself, thereby eliminating the need for persistent memory structures that would otherwise be required to maintain protocol state across multiple messages.
Solution Approach 2:
The state information traditionally maintained in memory by state-full protocols is extracted and embedded directly into the message structure itself. Message context, including reliability state information, is explicitly included in the message payload or headers, allowing the protocol handler to be state-less while still preserving reliability semantics through self-contained message context.
2Ease of operation
If mapping registries are used to map message keys to endpoint methods, then message routing can be achieved, but system complexity and processing overhead increase
Solution Approach 1:
The mapping registry infrastructure is completely removed from the system. Instead of maintaining separate registry data structures and lookup mechanisms, the message key to endpoint method mapping is directly embedded in the Web service data structures. The message key serves as a direct index or identifier that immediately resolves to the corresponding endpoint method without requiring intermediate registry lookups.
Solution Approach 2:
The mapping registry functionality is merged into the Web service data structure itself. The Web service data structure is extended to include direct mapping information between message keys and endpoint methods, eliminating the need for separate registry components and reducing system complexity by consolidating routing logic within the existing data model.
3Adaptability or versatility
If indirect communication between protocols and runtime object is used, then protocol independence can be maintained, but communication efficiency and performance deteriorate
Solution Approach 1:
A standardized protocol interface acts as an intermediary between diverse protocol handlers and the runtime object. This interface defines a common set of method signatures and data structures that all protocols must implement, allowing the runtime object to communicate with any protocol through a uniform interface without requiring protocol-specific code. This maintains protocol independence while enabling direct, efficient communication through the standardized interface rather than indirect communication paths.
Data Source
AI summary
A method is described that involves creating a reliable messaging object that includes a configuration context object. The reliable messaging object is created by reading configuration data from the configuration context object and writing instructions for delivery of the reliable messaging object based on the configuration data. The reliable messaging object is received in a messaging system independent from a web services runtime framework. The reliable messaging object is processed in the messaging system by placing the reliable messaging object into a queue and performing a quality of service check on the reliable messaging object.