Messaging Queue Spinning Engine Virtualization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current messaging queues are difficult to transition seamlessly between servers, leading to inefficiencies and increased likelihood of Service Level Agreement (SLA) violations due to their server-specific nature.

Innovation Solution

A message spinning engine that utilizes virtualized environments to route messages between business applications by determining mappings between source and recipient applications, selecting messaging servers based on load balancing and health checks, and generating performance reports, allowing for seamless transitions and adjustments in service levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If messaging queues are tied to a particular server, then they can be installed and operated on specific hardware, but transitioning messaging queues between servers becomes extremely difficult and error-prone

Engineering Contradiction:

ImproveEase of deploymentVSAvoidServer portability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a messaging queue management system that acts as an intermediary between the messaging queue and the physical server. This management system abstracts the messaging queue from server-specific dependencies, enabling seamless transitions and portability across different servers while maintaining operational continuity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The messaging queue management system provides universal functionality that allows messaging queues to operate across multiple different server environments. By creating a server-agnostic layer, the system enables messaging queues to be deployed, managed, and transitioned across various hardware platforms without being bound to a particular server configuration.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Productivity

If messaging queues are transitioned between servers, then server utilization can be optimized, but the transition process is time-consuming and increases SLA violation likelihood

Engineering Contradiction:

ImproveServer utilization efficiencyVSAvoidTransition time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The management system performs preliminary actions by pre-configuring and validating messaging queue transitions before they are executed. This includes preparing the target server environment, establishing connections in advance, and verifying readiness, which significantly reduces the actual transition time and minimizes service disruption.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous messaging queue operation during transitions by implementing seamless handover mechanisms. Messages are routed continuously through the management system, ensuring no interruption in service while the underlying server infrastructure is being transitioned, thus preventing SLA violations.

Inventive Principle:

Principle #20Continuity of useful action

3Productivity

If messaging queues are transitioned between servers, then resource allocation can be optimized, but service availability decreases during transition

Engineering Contradiction:

ImproveResource allocation efficiencyVSAvoidService availability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The management system serves as a mediator that maintains service availability during transitions by absorbing and managing the transition process. It continues to route messages and manage queue operations throughout the transition, ensuring that service availability is maintained even as the underlying server infrastructure changes.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements beforehand cushioning by preparing backup pathways and redundant routing mechanisms before transitions occur. This ensures that if issues arise during transition, service availability is protected through pre-established fallback options, minimizing the impact on reliability.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10439901B2Messaging queue spinning engine

Publication Date: 2019.10.08 BANK OF AMERICA CORP

AI summary

Systems are provided for using a message spinning engine to create and/or manage messaging queues in a distributed network using virtualized servers. An abstraction layer formed by virtualized servers may enable the message spinning engine to seamlessly transition messaging queues while minimizing the likelihood of exceeding the parameters of existing service level agreements. The message spinning engine may include a service mapping module to maintain mappings between source business applications and virtualized servers, a product bridge to implement message encapsulation for communication between different messaging queue products, and a messaging queue monitoring console to analyze performance and capacity of physical services and messaging services and accordingly adjust levels of service for source business applications.