Controller Message Listener Distributed Architecture Maintenance

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In distributed architectures, maintenance on servers often requires them to be taken offline, leading to unavailability and downtime, as existing systems lack efficient methods to control message flow across multiple servers and data centers.

Innovation Solution

A system and method for controlling message flow through a distributed architecture, where a controller communicates with message listeners to execute start or stop actions, allowing for remote management of message listeners, enabling rolling deployments and disaster recovery by rerouting message traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of repair

If a server is taken offline for maintenance, then the server can be maintained, but the server becomes unavailable and causes downtime

Engineering Contradiction:

Improveserver maintenanceVSAvoidserver availability

Core Design Contradiction:

Ease of repairVSReliability

Solution Approach 1:

The system segments the server functionality by separating the message listener component from the server itself. This allows the message listener to be independently controlled and restarted without taking the entire server offline, enabling maintenance while preserving server availability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by establishing a controller connection with the message listener before maintenance begins. This allows for coordinated shutdown and restart operations that minimize downtime and ensure smooth transitions during maintenance activities.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If message flow control is implemented across distributed architecture, then traffic rerouting and rolling deployments are enabled, but system complexity increases

Engineering Contradiction:

Improvetraffic rerouting capabilityVSAvoidcontrol system complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The controller serves as an intermediary component that manages message flow between message listeners and the distributed system. This centralized mediation simplifies the complexity by providing a single point of control rather than requiring complex peer-to-peer coordination across multiple servers.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The controller is designed with universal functionality to handle multiple operations including starting, stopping, and rerouting message listeners across different servers and data centers. This multi-functionality reduces overall system complexity by consolidating control capabilities in a single component.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10644934B1Systems and methods for controlling message flow throughout a distributed architecture

Publication Date: 2020.05.05 JPMORGAN CHASE BANK NA

AI summary

Systems and methods for controlling message flow throughout a distributed architecture are disclosed. In one embodiment, a method for controlling message flow throughout a distributed architecture may include (1) receiving, at a controller executed by a computer processor, a request comprising an identification of a desired server in a network of a plurality of servers and a desired action for the desired server to take; (2) the controller establishing a connection with a message listener associated with the desired server; (3) the controller communicating the message to the message listener; (4) the message listener executing the desired action; and (5) the message listener communicating a status of the desired server to the controller.