Messaging Queue API Optimizer Reduces Coding Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face significant challenges in correctly interfacing applications with messaging queue services due to the complexity of messaging queue service APIs, leading to application interruptions and errors.

Innovation Solution

An information handling system with a messaging queue service API optimizer that simplifies the process by executing a single command to connect and open message queues, reducing the complexity of coding and minimizing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If developers use traditional messaging queue service APIs, then the service provides comprehensive messaging functionality, but the API complexity increases significantly making it difficult to code correctly

Engineering Contradiction:
Improvemessaging functionalityVSAvoidAPI complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the messaging queue service API optimizer) that sits between the application and the traditional messaging queue service API. This intermediary simplifies the interface by providing a reduced set of optimized API commands that automatically translate to the underlying complex API operations, thereby maintaining comprehensive messaging functionality while reducing API complexity for developers

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the complex messaging queue service API into distinct functional layers: the simplified optimizer API layer that developers interact with, and the underlying traditional API layer that handles comprehensive messaging operations. This segmentation allows the system to expose only essential, simplified commands while hiding the complexity of the full API

Inventive Principle:
Principle #1Segmentation

2Reliability

If developers code comprehensive messaging queue service APIs, then full messaging functionality is achieved, but the coding time and effort increase significantly

Engineering Contradiction:
Improvemessaging functionalityVSAvoidcoding time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring and pre-compiling the complex API sequences into optimized command templates. When a developer issues a simple API command to the optimizer, the pre-prepared translation mappings automatically expand it into the correct sequence of underlying API calls, eliminating the need for developers to manually code complex multi-step messaging operations and significantly reducing coding time

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the messaging queue service API provides detailed control options, then messaging functionality is enhanced, but the likelihood of incorrect usage and errors increases

Engineering Contradiction:
Improvemessaging control optionsVSAvoidusage correctness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent extracts and isolates the most commonly used and essential messaging operations into a simplified API subset. By taking out only the critical functions needed for typical messaging scenarios and presenting them through an optimized interface, the system maintains adaptability for common use cases while eliminating the complexity and error-prone nature of the full API with its numerous control options

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10326720B2Messaging queue service API optimization system
Publication Date: 2019.06.18 DELL PROD LP
  • US10326720B2 patent drawing
  • US10326720B2 patent drawing
  • US10326720B2 patent drawing

AI summary

A method of providing a message queue service includes a first request being received by a computing device from an application to connect to a messaging queue manager provided by a messaging queue service that manages a messaging queue for at least one application. The application connects to the messaging queue manager by executing a single connect API command that causes the execution of a first plurality of commands in a messaging queue service API that provide for a connection of the application to the messaging queue manager. A second request is received from the application to open a message queue. The message queue managed by the messaging queue manager opens by executing a single open queue API command that causes the execution of a second plurality of commands that provide for the opening of the message queue.