Viacheslav Guzev
← WORK

Network infrastructure at Ozon

Traffic processing, load balancing, protection, and the tooling needed to operate production networking systems.

Period
2025 — NOW
My role
Senior Software Engineer
Organisation
Ozon Tech

Context

I work in Ozon Tech’s network load-balancing team. My responsibilities include production traffic processing, DDoS protection, CDN traffic steering, and the development and release tooling around those systems.

Traffic processing and protection

I develop L4 load balancing and DDoS protection capabilities. I have also investigated and improved network-policy update performance in yanet, a DPDK-based traffic-forwarding system.

Maintaining networking systems

I maintain internal yanet and Envoy forks. This work includes upstream synchronisation, code review, release preparation, CI/CD configuration, and collecting feedback after deployments.

I built C++ build-and-test pipelines around the projects’ Bazel and Meson build systems. This work supports the ongoing maintenance of the networking stack.

Load balancing and ingress migration

I worked on consistent-hash and subset-based balancing in Envoy to support session affinity during ingress migration. This required coordinating behaviour across components in the traffic path.

CDN traffic engineering

I develop collection and aggregation of client-side CDN measurements in ClickHouse. The measurements inform recommendations about where frontend and mobile clients should retrieve content, with the aim of improving delivery under changing network conditions.

Kubernetes tooling

I designed and implemented a cross-cluster CronJob controller in Go using controller-runtime. The work covered workload investigation, controller architecture, reconciliation and scheduling, local simulations, and presentations of the proposed approach.

Read about the controller.

I also evaluated approaches to macOS device management, comparing protocol capabilities and implementation options and presenting the trade-offs to management.

Scope

These descriptions focus on my engineering responsibilities. Deployment-scale figures, internal configurations, and attack-response mechanisms are not included.