Message Queue Server for Distributed Controller Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed controller systems, the complexity of reading and transmitting information from queues becomes complicated when the number of controllers or applications increases or decreases, leading to inefficiencies in scalability and load balancing due to the generation of queues per process, which affects the flexibility and efficiency of the messaging system.
Innovation Solution
A server configuration where queues are generated per switch, with each controller receiving destination information to transmit read information to the appropriate controller, and multiple MQ servers with the same queue structure are used to distribute messages, simplifying the process of reading and transmitting information and improving scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If queues are generated per process (controller or application), then the messaging system can support distributed controller architecture, but the process of reading and transmitting information from queues becomes complicated when the number of controllers or applications increases or decreases
Solution Approach 1:
The patent introduces a message queue server as an intermediary component that manages queues independently from controllers and applications. The server receives information from applications, stores it in appropriate queues, and transmits it to controllers based on destination information. This mediator approach decouples the complexity of queue management from the controllers and applications, allowing them to scale without increasing process complexity.
Solution Approach 2:
The patent extracts the queue management functionality from the controllers and applications themselves, centralizing it in the message queue server. By taking out the queue reading and transmitting processes from the distributed controller logic and consolidating them in a dedicated server, the system achieves simplified processes that remain consistent regardless of the number of controllers or applications.
2Productivity
If the number of processes (controllers, applications) is increased to improve throughput, then system throughput is improved, but the queue management process becomes more complicated due to per-process queue generation
Solution Approach 1:
The message queue server performs multiple functions: receiving information from applications, determining destination controllers, storing information in queues, and transmitting information to controllers. This universal component handles all queue management operations regardless of the number of controllers or applications, allowing the system to scale for improved throughput without increasing queue management complexity.
3Reliability
If queues are managed per process basis, then each process has dedicated information storage, but the process of allocating information to multiple queues becomes complicated when there are multiple applications for load sharing
Solution Approach 1:
The message queue server acts as an intermediary that receives information destined for multiple applications and automatically allocates it to the appropriate queues. The server uses destination information to determine which queues should receive the information and performs the allocation without requiring complex logic in the controllers or applications, thus maintaining dedicated information storage while simplifying the allocation process.
Data Source
AI summary
A server is provided in a network system that controllers control switches based on information given from an application. The server includes queues, each of which is associated with the switches, to store information given from the application directed to the associated switch, a receiver to receive, from each controller, destination information including queue designating information and information for transmitting information read from the queue designated by the queue designating information to one of the controllers being a destination of the read information, and a transmitter to transmit the information read from each of the queues to one of the controllers to control at least one of the switches associated with each of the queues based on the destination information.