Stateless Protocol Instance Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Web services message processing runtime frameworks lack efficiency in handling concurrent message processing and ensuring reliable messaging due to state-full protocols and the need for extensive resource allocation, which hampers scalability and performance.
Innovation Solution
The improved runtime framework eliminates the mapping registry and context intermediary, redesigns protocols to be state-less, and supports hibernation, enabling efficient processing of multiple message pairs with a single protocol instance and enhancing reliability through state-less WS-Reliable Messaging protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state-full protocols are used to ensure reliable messaging, then messaging reliability is improved, but resource allocation increases and scalability deteriorates
Solution Approach 1:
The protocol processing is segmented into protocol instances that can be independently created and destroyed. Each protocol instance handles a specific message pair, allowing the system to allocate resources only when needed and release them afterward, thus maintaining reliability without permanent resource allocation overhead
Solution Approach 2:
The system dynamically creates protocol instances based on message arrival and destroys them after processing. This dynamic allocation allows the system to adapt resource usage to actual workload, improving scalability while maintaining reliability through protocol instance state management
2Reliability
If extensive resource allocation is made for each message processing, then messaging reliability is improved, but processing efficiency deteriorates
Solution Approach 1:
Protocol instances are pre-configured with necessary processing logic and state management capabilities before message arrival. This preliminary preparation allows efficient message processing without requiring extensive resource allocation at message processing time, thus improving both reliability and efficiency
Solution Approach 2:
After a protocol instance completes message processing, its resources are released and the instance is destroyed. This discard-and-recreate approach ensures that each message receives dedicated protocol processing (maintaining reliability) while avoiding the overhead of maintaining permanent protocol instances for all possible messages (improving efficiency)
3Productivity
If a single protocol instance handles multiple message pairs, then scalability is improved, but message processing complexity increases
Solution Approach 1:
The protocol instance is designed as a universal component that can handle multiple different message pairs through parameterization. The same protocol instance logic is reused across different messages, achieving scalability while managing complexity through standardized processing patterns and state management
Data Source
AI summary
A system and method for the lifecycle of a protocol processing a message is described. In one embodiment, a stateless protocol instance is registered with an objected-oriented environment and a stateless protocol context instance is invoked to process a message.