Hybrid Middleware Thread Transformer for Resource Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing middleware solutions often lead to inefficient resource usage and redundancy due to the need for separate thread-based and process-based servers, which increases latency and deployment costs, especially when handling requests from multiple programming languages and environments.

Innovation Solution

The implementation of hybrid middleware that includes a thread transformer, which intercepts requests from process-based clients and converts them into merged requests for a single thread-based server, reducing the need for redundant thread-based servers and optimizing resource usage by allowing a single thread-based server to handle requests from multiple processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate thread-based servers are deployed for each process-based middleware instance, then compatibility with multiple programming languages and environments is maintained, but resource usage becomes inefficient and deployment costs increase

Engineering Contradiction:

Improvecompatibility with multiple programming languagesVSAvoidnumber of thread-based servers

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple separate thread-based servers into a single unified thread-based server that can handle requests from multiple process-based middleware instances. The thread transformer converts requests from different process-based clients into a standardized format that the single thread-based server can process, eliminating the need for separate servers for each process-based instance while maintaining compatibility with various programming languages and environments.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The single thread-based server is designed with universal capabilities to handle requests from multiple process-based middleware instances running different programming languages. The thread transformer acts as a universal interface that adapts requests from various sources (COBOL, Java, C++, etc.) into a format the thread-based server can process, making the server multi-functional rather than requiring dedicated servers for each language or environment.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate thread-based servers are used for each process-based middleware, then language-specific requirements are met, but latency increases due to multiple server hops

Engineering Contradiction:

Improvelanguage-specific requirementsVSAvoidrequest processing latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

By consolidating multiple thread-based servers into one, the patent reduces the number of server hops in the request processing chain. Instead of routing requests through separate servers for each process-based middleware instance, all requests are funneled through a single thread transformer and then to a single thread-based server, significantly reducing latency while still meeting language-specific requirements through the transformer's adaptation capabilities.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If multiple thread-based servers are deployed to handle requests from different process-based clients, then service reliability is maintained, but deployment costs increase

Engineering Contradiction:

Improveservice reliabilityVSAvoiddeployment cost

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The patent merges multiple expensive server deployments into a single cost-effective solution. By using one thread-based server with a thread transformer that handles multiple process-based clients, organizations avoid the high deployment costs associated with running separate thread-based servers for each process-based middleware instance, while maintaining service reliability through the robust request handling capabilities of the unified architecture.

Inventive Principle:

Principle #5Merging (Combining)

4Productivity

If redundant thread-based servers are maintained for each process-based middleware, then request handling capacity is sufficient, but resource efficiency decreases

Engineering Contradiction:

Improverequest handling capacityVSAvoidresource efficiency

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The single thread-based server is designed with universal handling capabilities that allow it to process requests from multiple process-based middleware instances simultaneously. The thread transformer efficiently converts and routes requests, enabling the single server to maintain sufficient request handling capacity for all clients without the resource waste of running multiple redundant servers, thereby improving overall resource efficiency.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10440137B2Efficient usage of resources in multiple middleware environments

Publication Date: 2019.10.08 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A first request to a first thread-based server from a first thread-based client is detected. The first request is derived by the first thread-based client in response to a first call from a first user program running on process-based middleware. The first request is intercepted from a communication pathway. The first request is converted to a merged request. The merged request is intended for a merged thread-based server of the thread-based middleware. The merged request is sent to the merged thread-based server.