Virtualized Broker Clusters With Proxy-Based Transparent Rebalancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management and orchestration of large, dynamically fluctuating streams of data in virtualized computing environments face challenges such as resource imbalances leading to performance issues and underutilization, with re-scaling and re-balancing often disrupting data transmission and consumption.

Innovation Solution

A data streaming service utilizing virtualized broker clusters with a front-end proxy layer and back-end broker layer, where client-facing broker IDs are maintained by proxy computing instances, allowing transparent scaling, re-balancing, and resource management without disrupting data producing or consuming clients, using metadata services and stores to manage mappings between client-facing and internal broker IDs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If re-scaling and re-balancing are performed to address resource imbalances, then resource utilization is optimized, but data transmission and consumption are interrupted

Engineering Contradiction:
Improveresource utilizationVSAvoiddata transmission continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The broker cluster is segmented into multiple independent broker instances, each capable of handling data streams. This allows individual brokers to be scaled, re-balanced, or replaced without affecting the entire cluster's operation, thus optimizing resource utilization while maintaining continuous data transmission through other healthy brokers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A coordinator entity is introduced as an intermediary between clients and broker instances. This coordinator manages the mapping between client connections and specific broker instances, enabling transparent re-scaling and re-balancing operations. When brokers are reconfigured, the coordinator updates mappings without interrupting client data transmission or consumption operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If more resources are added to handle increasing workloads, then system capacity is improved, but system complexity increases

Engineering Contradiction:
Improvesystem capacityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Broker instances are designed as universal, standardized components that can perform multiple functions (data production, consumption, re-balancing). This modularity allows resources to be added uniformly without increasing system complexity, as each new broker integrates using the same protocols and interfaces as existing brokers.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The broker cluster implements self-service mechanisms where brokers automatically register with the coordinator, report their capacity status, and participate in load balancing decisions. This automation reduces the operational complexity of managing scaled resources, as the system self-configures when new brokers are added rather than requiring manual configuration management.

Inventive Principle:
Principle #25Self-service

3Productivity

If re-balancing is performed to address imbalances, then performance is improved, but client connections are disrupted

Engineering Contradiction:
ImproveperformanceVSAvoidclient connection stability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The coordinator acts as an intermediary that abstracts the re-balancing process from clients. When re-balancing is needed, the coordinator manages the migration of client connections to different brokers transparently, maintaining stable client connections while redistributing workloads to improve performance. Clients interact only with the coordinator, not directly with individual brokers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-establishing connection pools and maintaining backup broker assignments before re-balancing operations. This allows smooth transitions during re-balancing, as clients can be gradually migrated to new broker assignments without abrupt connection disruptions, thereby improving performance while maintaining connection stability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250294082A1Data Streaming Service with Virtualized Broker Clusters
Publication Date: 2025.09.18 AMAZON TECH INC
  • US20250294082A1 patent drawing
  • US20250294082A1 patent drawing
  • US20250294082A1 patent drawing

AI summary

Various embodiments of systems and methods for providing virtualized (e.g., serverless) broker clusters for a data streaming service are disclosed. A data streaming service uses a front-end proxy layer and a back-end broker layer to provide virtualized broker clusters, for example in a Kafka-based streaming service. Resources included in a virtualized broker cluster are monitored and automatically scaled-up, scaled-down, or re-balanced in a way that is transparent to data producing and/or data consuming clients of the data streaming service.