Perfil de habilidad

Load Balancing

L4/L7 load balancing, HAProxy, NGINX, AWS ALB/NLB, health checks, algorithms

Cloud & Infrastructure DNS & Networking

Roles

7

donde aparece esta habilidad

Niveles

5

ruta de crecimiento estructurada

Requisitos obligatorios

27

los otros 8 opcionales

Dominio

Cloud & Infrastructure

skills.group

DNS & Networking

Última actualización

17/3/2026

Cómo usar

Selecciona tu nivel actual y compara las expectativas.

Qué se espera en cada nivel

La tabla muestra cómo crece la profundidad desde Junior hasta Principal.

Rol Obligatorio Descripción
Cloud Engineer Obligatorio Understands basic load balancing concepts in cloud: ALB/NLB in AWS, Azure Load Balancer, and health check configurations. Follows team guidelines for setting up target groups and SSL termination in managed load balancer services.
DevOps Engineer Understands load balancing principles: round-robin, least connections, health checks. Knows the difference between L4 and L7 balancers, understands the role of ALB/NLB in AWS. Configures basic Kubernetes Service of LoadBalancer type.
Game Server Developer Understands basic Load Balancing concepts. Uses ready-made configurations. Performs simple operations under senior guidance.
Infrastructure Engineer Understands basic load balancing concepts: round-robin, least-connections algorithms, and L4/L7 load balancers. Follows team procedures for configuring Nginx/HAProxy and monitoring backend health with basic health check endpoints.
Network Engineer Obligatorio Knows basic load balancing concepts for network engineering and can apply them in typical tasks. Uses standard tools and follows established team practices. Understands when and why this approach is used.
Platform Engineer Obligatorio Configures Application Load Balancer for platform services: target groups, health checks, routing rules. Understands the difference between ALB/NLB/CLB and their use cases. Configures SSL termination and redirect rules. Debugs 502/503 errors through CloudWatch metrics.
Site Reliability Engineer (SRE) Understands load balancing: Layer 4 vs Layer 7, health checks, round-robin. Configures ALB/NLB in AWS. Monitors load balancer metrics: request count, latency, error rate.
Rol Obligatorio Descripción
Cloud Engineer Obligatorio Independently configures cloud load balancing: multi-AZ ALB with path-based routing, weighted target groups for canary deployments, and WAF integration. Implements auto-scaling policies triggered by load balancer request metrics.
DevOps Engineer Configures load balancers: AWS ALB/NLB with target groups, Nginx Ingress in Kubernetes, HAProxy. Configures SSL termination, sticky sessions, health checks. Manages Ingress resources with annotations for different controllers.
Game Server Developer Independently configures and manages Load Balancing. Writes IaC for standard tasks. Understands networking and security basics.
Infrastructure Engineer Independently configures load balancing with Nginx/HAProxy/Envoy: upstream configurations, session persistence, rate limiting, and SSL/TLS termination. Implements IaC for load balancer provisioning and monitoring dashboards for traffic distribution.
Network Engineer Obligatorio Confidently applies load balancing for network engineering in non-standard tasks. Independently selects the optimal approach and tools. Analyzes trade-offs and proposes improvements to existing solutions.
Platform Engineer Obligatorio Designs load balancing for the platform: weighted routing for canary, path-based routing for multi-service. Configures global load balancing (Route53, Global Accelerator). Optimizes connection draining and idle timeout. Implements WAF at load balancer level for platform protection.
Site Reliability Engineer (SRE) Manages load balancers: target groups, weighted routing, TLS termination. Configures advanced health checks. Implements canary deployments through traffic shifting. Diagnoses 502/503 errors.
Rol Obligatorio Descripción
Cloud Engineer Obligatorio Designs infrastructure solutions with Load Balancing. Optimizes cost and performance. Introduces best practices and security hardening.
DevOps Engineer Obligatorio Designs load balancing architecture for production: multi-level LB (Global → Regional → Pod), GSLB for geo-distribution, circuit breaking. Configures advanced routing through Istio/Envoy, optimizes for latency and throughput.
Game Server Developer Obligatorio Designs load balancing architecture for game servers: player session affinity, matchmaking-aware routing, and geographic proximity-based server selection. Optimizes for low-latency UDP load balancing and graceful server draining during updates.
Infrastructure Engineer Obligatorio Designs load balancing architecture for high-traffic systems: ECMP routing, DPDK-accelerated proxying, and global server load balancing (GSLB). Optimizes for minimal latency with connection pooling, keep-alive tuning, and hardware offloading.
Network Engineer Obligatorio Expertly applies load balancing for network engineering to design complex systems. Optimizes existing solutions and prevents architectural mistakes. Conducts code reviews and trains colleagues on best practices.
Platform Engineer Obligatorio Develops traffic management architecture for IDP: multi-layer balancing (DNS → GLB → ALB → service mesh). Implements circuit breaking and rate limiting at platform level. Creates self-service load balancer provisioning through Terraform modules for teams.
Site Reliability Engineer (SRE) Obligatorio Designs load balancing architecture: global load balancing (Route53, Cloudflare), internal LB for microservices, gRPC balancing. Optimizes connection draining, session affinity, retry policies.
Rol Obligatorio Descripción
Cloud Engineer Obligatorio Defines load balancing strategy for cloud platform: multi-region traffic management, failover automation, and cost-optimized balancer selection. Establishes IaC standards for load balancer provisioning and conducts architecture reviews.
DevOps Engineer Obligatorio Defines organizational load balancing strategy: standards for all service types, configuration automation, service mesh integration. Designs global traffic architecture considering disaster recovery and multi-region failover.
Game Server Developer Obligatorio Defines infrastructure strategy with Load Balancing. Establishes IaC standards. Conducts architecture reviews. Optimizes FinOps.
Infrastructure Engineer Obligatorio Defines load balancing infrastructure strategy: balancer technology selection (hardware vs software), HA configuration standards, and capacity planning for traffic growth. Establishes monitoring, alerting, and incident response procedures for load balancer failures.
Network Engineer Obligatorio Establishes load balancing standards for the network engineering team and makes architectural decisions. Defines the technical roadmap incorporating this skill. Mentors senior engineers and influences practices of adjacent teams.
Platform Engineer Obligatorio Defines organizational traffic management strategy: API gateway, service mesh, load balancing as unified architecture. Leads progressive delivery adoption through traffic shifting. Designs multi-region active-active with intelligent failover for critical services.
Site Reliability Engineer (SRE) Obligatorio Defines LB standards: health check requirements, failover procedures, capacity planning. Implements automated traffic management. Conducts load testing and failure mode analysis.
Rol Obligatorio Descripción
Cloud Engineer Obligatorio Defines platform-level load balancing strategy: L4 (NLB) vs L7 (ALB) vs Global (GCLB), multi-region load balancing with GeoDNS, service mesh for internal traffic. Designs zero-downtime deployment patterns and traffic management architecture for canary/blue-green releases.
DevOps Engineer Obligatorio Develops global traffic management architecture: intelligent load balancing with ML, multi-cloud traffic management, standards for thousands of services. Defines routing platform with automatic failover, canary routing and A/B testing at infrastructure level.
Game Server Developer Obligatorio Defines the organization's cloud strategy. Evaluates multi-cloud vs single-cloud. Designs enterprise-grade infrastructure. Establishes FinOps practices.
Infrastructure Engineer Obligatorio Defines organizational load balancing strategy: L4/L7 balancing architecture, Global Server Load Balancing between regions, choosing between cloud ALB/NLB and self-hosted HAProxy/Envoy. Designs health check standards, graceful draining and circuit breaking for critical services.
Network Engineer Obligatorio Shapes load balancing strategy for network engineering at the organizational level. Defines best practices and influences technology choices beyond their own team. Is a recognized expert in this area.
Platform Engineer Obligatorio Shapes vision for intelligent traffic management: ML-based routing, predictive autoscaling, self-healing infrastructure. Defines unified data plane strategy for the organization. Evaluates emerging approaches to traffic engineering for scaling the platform globally.
Site Reliability Engineer (SRE) Obligatorio Designs traffic management strategy: global server load balancing, multi-CDN, anycast. Defines traffic engineering patterns for multi-region availability and disaster recovery.

Comunidad

👁 Seguir ✏️ Sugerir cambio Inicia sesión para sugerir cambios
📋 Propuestas
Aún no hay propuestas para Load Balancing
Cargando comentarios...