Web Services Hibernation via Stateless Protocol Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Web services message processing runtime frameworks lack efficiency in handling business models requiring confidentiality, ordered message processing, and support for diverse transport protocols, while also being inefficient in resource utilization due to state-full protocols and dependency on mapping registries.
Innovation Solution
The improved runtime framework eliminates the mapping registry, redesigns protocols to be state-less, and allows direct communication between protocols and the runtime object, enabling hibernation and efficient processing of messages across different transport protocols through state-less protocols and optimized message handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If state-full protocols are used to handle confidential and ordered message processing, then reliability is improved, but memory consumption increases and scalability deteriorates
Solution Approach 1:
The protocol processing is segmented into state-less protocol layers that handle specific aspects of message processing independently. Each protocol layer processes messages without maintaining internal state, dividing the complex state-full protocol into multiple state-less components that collectively achieve reliable message processing through standardized interfaces and systematic handling of confidential and ordered messages
Solution Approach 2:
Instead of maintaining state in memory through state-full protocols, the system creates standardized copies of message data structures that can be processed and discarded. Message contexts are copied and passed through the protocol stack without requiring persistent state storage, reducing memory consumption while maintaining processing reliability
2Adaptability or versatility
If mapping registries are used to manage protocol implementations, then adaptability is improved, but system complexity and processing overhead increase
Solution Approach 1:
The mapping registry is extracted and replaced with direct protocol implementation classes that are instantiated and invoked directly. The complex registry lookup mechanism is removed, and protocols are managed through straightforward object-oriented instantiation and interface implementation, reducing system complexity while maintaining adaptability through polymorphic protocol handlers
Solution Approach 2:
Protocol implementations are designed to be self-configuring and self-registering through standardized interfaces rather than requiring external mapping registries. The system automatically manages protocol instances through interface-based discovery and instantiation, eliminating the need for complex registry maintenance while preserving adaptability
3Productivity
If state-less protocols are used to reduce memory consumption, then resource utilization is improved, but support for ordered message processing becomes more difficult
Solution Approach 1:
A message context intermediary structure is introduced that carries ordering information and processing state through the state-less protocol stack. This intermediary maintains the necessary ordering metadata without requiring the protocols themselves to be state-full, enabling ordered message processing while preserving resource efficiency through state-less protocol implementations
Data Source
AI summary
A method is described that involves comprising, during runtime in an object-oriented environment, invoking, from an object, a first Web services endpoint method to process a first message by: invoking the first Web services endpoint method through a first interface according to an endpoint method invocation format, where, the first Web services endpoint method is implemented with a first component that is provided one or more services by a first container. The method also involves invoking, from the object, a second Web services endpoint method to process a second message by: invoking the second Web services endpoint method through a second interface according to the endpoint method invocation format. The second Web services endpoint method is implemented with a second component that is provided one or more services by a second container. The first and second containers have respective interfaces that are different.