spring-cloud/spring-cloud-netflix

Document Load Balancing in Spring Cloud Netflix

Open

#4,527 opened on Jan 23, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (2,433 forks)batch import
documentationhelp wanted

Repository metrics

Stars
 (4,805 stars)
PR merge metrics
 (Avg merge 2d 6h) (5 merged PRs in 30d)

Description

Documentation Request: Load Balancing in Spring Cloud Netflix

Overview

Spring Cloud Netflix provides integrated load balancing capabilities primarily via Spring Cloud LoadBalancer and Eureka service discovery. Clear documentation will help users understand:

  • How load balancing works with Eureka and Spring Cloud LoadBalancer
  • Key configuration properties
  • Zone-preference logic and metadata
  • How to enable/disable or customize load balancing for services
  • Best practices and common pitfalls

Core Areas to Cover

  • Spring Cloud LoadBalancer Usage
    • How service instances are selected for requests
    • Relationship to DiscoveryClient and logical Eureka service identifiers (VIPs)
  • Zone Preference and Configuration
    • How zone is determined (instance metadata, hostname, client config)
    • The role of spring.cloud.loadbalancer.eureka.approximateZoneFromHostname
  • Properties and Customization
    • Main configuration properties (with sample values)
    • Example YAML/Java configuration snippets
  • Eureka Metadata & Filtering
    • Use of eureka.instance.metadataMap.zone
  • Troubleshooting Tips
    • Common misconfigurations
    • How to verify load balancing behavior in logs
  • References to Source Code

Benefit

Improved documentation will assist users in comprehending, enabling, and troubleshooting load balancing in Spring Cloud Netflix microservice deployments.

Contributor guide

Research direction
Examine the referenced source code files (EurekaLoadBalancerProperties.java and EurekaLoadBalancerClientConfiguration.java) and describe how load balancing is configured and used in Spring Cloud Netflix. Include configuration properties, zone preference, and troubleshooting tips.
Tech stack
javaspring
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70