0Pricing
Spring Boot 4 Microservices & REST APIs · Aula

Balanceamento de carga no cliente com Ribbon

Integre o Ribbon para realizar balanceamento de carga no cliente entre várias instâncias de serviços.

Balanceamento de carga no cliente com Ribbon é uma aula grátis de Spring Boot 4 Microservices & REST APIs no CoddyKit. Esta é a aula 2 de 3. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Spring Boot 4 Microservices & REST APIs, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Boot 4 Microservices & REST APIs inclui 3 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

What is Load Balancing?

In a microservices world, applications often have multiple copies (instances) of the same service running. This is for scalability and high availability.

Load balancing is the process of distributing incoming network traffic across these multiple instances. It ensures no single service instance gets overwhelmed.

  • Scalability: Handle more users by adding more instances.
  • High Availability: If one instance fails, others can take over.
  • Performance: Distribute work evenly to reduce response times.

Client-Side vs. Server-Side LB

There are two main types of load balancing:

  • Server-Side Load Balancing: A dedicated component (like Nginx or a hardware load balancer) sits in front of your services. Clients send requests to this component, and it forwards them to an appropriate service instance.
  • Client-Side Load Balancing: The client application itself is responsible for knowing about all available service instances and choosing one for each request. This is where tools like Ribbon come in!

Ribbon: Your Client-Side Helper

Ribbon is a client-side load balancer that integrates seamlessly with Spring Cloud applications. It helps your client service pick the right instance of a target service.

How does Ribbon know about service instances? It works hand-in-hand with a service discovery mechanism, like Eureka. Eureka tells Ribbon where services are, and Ribbon decides which one to call.

Adding Load Balancing Dependency

To enable client-side load balancing in your Spring Boot application, you typically include the Spring Cloud LoadBalancer dependency. While 'Ribbon' is in the lesson title, Spring Cloud LoadBalancer is its modern successor and works similarly.

Add this to your pom.xml:

<dependency>
  <groupId>org.springframework.cloud</groupId>
  <artifactId>spring-cloud-starter-loadbalancer</artifactId>
</dependency>

Load Balanced RestTemplate

The easiest way to use client-side load balancing is with Spring's RestTemplate. By simply adding the @LoadBalanced annotation to your RestTemplate bean, Spring configures it to use a load balancer.

When you make an HTTP call, you'll use the logical service name (e.g., my-service) instead of a specific IP address and port. The load balancer (Ribbon/Spring Cloud LoadBalancer) resolves this name to a real instance.

Client Calling a Service (Code)

Here's a simple Spring Boot client application that uses a load-balanced RestTemplate to call another service named my-service. For this to work, my-service must be registered with a service discovery server (like Eureka).

package com.coddykit;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.client.loadbalancer.LoadBalanced;
import org.springframework.context.annotation.Bean;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.client.RestTemplate;

@SpringBootApplication
@RestController
public class MyClientApplication {

    private final RestTemplate restTemplate;

    // Inject the load-balanced RestTemplate
    public MyClientApplication(@LoadBalanced RestTemplate restTemplate) {
        this.restTemplate = restTemplate;
    }

    public static void main(String[] args) {
        SpringApplication.run(MyClientApplication.class, args);
    }

    // Define the load-balanced RestTemplate bean
    @Bean
    @LoadBalanced 
    public RestTemplate restTemplate() {
        return new RestTemplate();
    }

    // Endpoint to call 'my-service'
    @GetMapping("/call-my-service")
    public String callMyService() {
        // Use the logical service ID 'my-service'
        return restTemplate.getForObject("http://my-service/hello", String.class);
    }
}

Load Balancing Algorithms

Ribbon (and Spring Cloud LoadBalancer) can use different algorithms to decide which service instance to call. Some common ones include:

  • Round Robin: Distributes requests sequentially to each instance (e.g., instance 1, then 2, then 3, then 1 again).
  • Random: Picks a random instance for each request.
  • Availability Filtering: Ignores instances that are marked as down or unresponsive.
  • Weighted Response Time: Favors instances that have historically responded faster.

Configuring Load Balancing Rules

You can configure the load balancing rule for a specific service in your application.yml or application.properties. For example, to use a Round Robin rule for my-service (using older Ribbon config style):

my-service.ribbon.NFLoadBalancerRuleClassName=com.netflix.loadbalancer.RoundRobinRule

While this specific syntax is for older Ribbon, the concept of configuring rules per service is similar in Spring Cloud LoadBalancer, often done via custom configurations or properties.

Benefits of Client-Side LB

Client-side load balancing offers several advantages in a microservices architecture:

  • Simpler Infrastructure: No need for a separate hardware or software load balancer component.
  • Direct Communication: Clients communicate directly with service instances, potentially reducing latency.
  • Dynamic Scaling: Easily adapts to new service instances registering or deregistering with service discovery.
  • Granular Control: The client can implement custom load balancing logic or apply different rules per service.

Quick Check on Load Balancing

You've learned about client-side load balancing. Let's test your understanding.

Recap: Client-Side Load Balancing

Great job! You've explored client-side load balancing with Ribbon (and its successor, Spring Cloud LoadBalancer).

  • We learned that load balancing distributes traffic across service instances for scalability and availability.
  • Client-side load balancing means the client itself chooses which instance to call, often using a logical service name.
  • The @LoadBalanced annotation on a RestTemplate bean is key for enabling this feature in Spring Boot.
  • Various algorithms like Round Robin can be used to distribute requests.

This approach makes your microservices more robust and efficient!

Perguntas Frequentes

A aula “Balanceamento de carga no cliente com Ribbon” é grátis?

Sim — o texto completo de “Balanceamento de carga no cliente com Ribbon” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Spring Boot 4 Microservices & REST APIs, atualize para CoddyKit PRO. O curso de Spring Boot 4 Microservices & REST APIs inclui 3 aulas no total.

O que vou aprender em “Balanceamento de carga no cliente com Ribbon”?

Integre o Ribbon para realizar balanceamento de carga no cliente entre várias instâncias de serviços. Você pratica Spring Boot 4 Microservices & REST APIs com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Spring Boot 4 Microservices & REST APIs?

Nenhuma experiência prévia é necessária. Spring Boot 4 Microservices & REST APIs no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 3.

Quanto tempo leva a aula “Balanceamento de carga no cliente com Ribbon”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Spring Boot 4 Microservices & REST APIs?

Sim. Cada aula de Spring Boot 4 Microservices & REST APIs inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Implementando a descoberta de serviços com Eureka
  2. Balanceamento de carga no cliente com Ribbon
  3. Gateway de API com Spring Cloud Gateway
← Voltar para Spring Boot 4 Microservices & REST APIs