Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Network Load Balancer
  • Getting started
    • Overview
    • Network load balancer types
    • Listener
    • Targets and target groups
    • Health checks
    • Implementation specifics
    • Use cases
    • Best practices
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. Best practices

Best practices

Written by
Yandex Cloud
Updated at September 2, 2025

Use different availability zonesUse different availability zones

Create cloud resources in multiple availability zones. This way you can maintain the availability of your applications in case one of the zones becomes unavailable.

Allocate resources across zones uniformlyAllocate resources across zones uniformly

The same amount of cloud resources should be hosted in each availability zone. If there are three VMs in the ru-central1-a availability zone, the ru-central1-b and ru-central1-d availability zones should also host three VMs each.

Create cloud resources with redundancyCreate cloud resources with redundancy

If one of the VMs in a certain availability zone fails, that availability zone will continue receiving the same volume of traffic. This will increase the load on the remaining healthy VMs. To prevent all the VMs from failing, we recommend allocating extra resources in each availability zone in addition to the resources required for supporting the design load.

Assign a dedicated balancer to each appAssign a dedicated balancer to each app

When deploying multiple applications in Yandex Cloud, create an independent load balancer for each application.

Set up a multi-layer infrastructureSet up a multi-layer infrastructure

In some cases, such as organizing an MK8S multi-cluster, where a separate zonal cluster is deployed in each availability zone, you may need multi-level traffic distribution. At input, the traffic will be received by an L7 load balancer, which will distribute it to one of the zonal clusters. Next, at the zonal cluster level, the traffic will be received by a LoadBalancer type service (built around an L3 load balancer), and from there distributed among the relevant cluster pods for processing.

You can use the Application Load Balancer as an L7 load balancer.

You can use the Network Load Balancer as L3 load balancers.

The multi-level balancing schemes, where an L3 load balancer distributes traffic to L7 load balancers downstream of it, are not supported and are not recommended.

Use casesUse cases

  • Architecture and protection of a basic web service
  • Implementing fault-tolerant scenarios for NAT VMs
  • Running an autoscaling instance group
  • Migrating services from an NLB to L7 ALB for DDoS protection using Yandex Smart Web Security

Was the article helpful?

Previous
Use cases
Next
Quotas and limits
© 2025 Direct Cursus Technology L.L.C.