Collaborative Message Broker Scaling via Load Balancer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current messaging systems face challenges with scalability, availability, and migration, particularly in horizontal scaling and load balancing, which can lead to performance overhead and stability issues due to the need for costly coordination between brokers.

Innovation Solution

Implementing a collaborative message broker scaling and migration system that uses a load balancing component with a virtual provider entity representing a HA message broker pair, including a leader and follower entity, and a shared database for administration registry data store, allowing for secure, automatic, and efficient load balancing and migration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If horizontal scaling is implemented across multiple cloud resources, then the messaging system can support increasing workloads, but coordination overhead between brokers increases and negatively impacts stability and availability

Engineering Contradiction:
Improveworkload capacityVSAvoidsystem availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces a load balancing component as an intermediary that sits between client nodes and broker nodes. This mediator handles the coordination and distribution of messages, eliminating the need for direct peer-to-peer coordination between brokers. The load balancer abstracts the complexity of broker coordination, allowing horizontal scaling without the stability issues caused by direct broker-to-broker communication overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If coordination between all broker pairs is implemented for load balancing, then horizontal scaling is enabled, but performance overhead becomes costly

Engineering Contradiction:
Improvescaling capabilityVSAvoidsystem performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts the coordination function from the broker nodes themselves and places it in a dedicated load balancing component. By taking out the coordination responsibility from the brokers, the system enables horizontal scaling without imposing coordination overhead on the message processing path. Brokers focus solely on message handling while the load balancer handles coordination, thus maintaining high performance while achieving scalability.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If legacy single broker messaging systems are migrated to scalable solutions, then scalability improves, but migration causes significant downtime

Engineering Contradiction:
Improvesystem scalabilityVSAvoiddowntime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a migration mechanism where broker nodes are pre-configured and registered with the load balancing component before actual migration occurs. The administration registry data store maintains metadata about broker nodes, allowing the system to prepare migration paths in advance. This preliminary setup enables seamless switching between broker nodes during migration, minimizing downtime by having target brokers ready to immediately take over when switches occur.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If reconfiguration during runtime is enabled for migration, then operational flexibility improves, but system complexity increases

Engineering Contradiction:
Improveruntime reconfigurabilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The load balancing component serves as an intermediary that manages runtime reconfiguration transparently. When broker nodes need to be reconfigured or migrated, the load balancer handles the coordination, registration, and switching operations without requiring direct manual intervention or complex configuration changes in the broker nodes themselves. This abstraction layer simplifies runtime operations while maintaining the ability to dynamically reconfigure the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11399082B1Collaborative message broker scaling and migration
Publication Date: 2022.07.26 SAP SE
  • US11399082B1 patent drawing
  • US11399082B1 patent drawing
  • US11399082B1 patent drawing

AI summary

A client node may execute an application that communicates with a first messaging service component of a first broker node in a server segment and a second messaging service component of a second broker node in the server segment. A load balancing component is coupled to the client node, and a first virtual provider entity for the first messaging service component is coupled to the load balancing component. The first virtual provider entity may represent a first HA message broker pair, including: (i) a first leader message broker entity, and (ii) a first follower message broker entity to take control when there is a problem with the first leader message broker entity. A shared database is accessible by the first broker node, the first HA message broker pair, and the second broker node, and includes an administration registry data store.