Best of ByteByteGo — December 2025

1. 1
   Article

   ByteByteGo·19w

   How Reddit Migrated Comments Functionality from Python to Go

   Reddit migrated their comments functionality from a legacy Python monolith to a Go microservice, handling their largest dataset and highest write throughput. The migration used "tap compare" for read operations and "sister datastores" for writes, allowing validation with real traffic while maintaining zero risk. Key challenges included cross-language serialization issues, database access pattern differences, and race conditions in verification. The migration succeeded with zero user disruption and delivered an unexpected bonus: p99 latency was cut in half, dropping from occasional 15-second spikes to consistently under 100 milliseconds.

   235

   2
2. 2
   Article

   ByteByteGo·20w

   How Netflix Built a Distributed Write Ahead Log For Its Data Platform

   Netflix built a distributed Write-Ahead Log (WAL) system to solve data reliability issues across their platform. The WAL captures every data change before applying it to databases, enabling automatic retries, cross-region replication, and multi-partition consistency. Built on top of their Data Gateway Infrastructure, it uses Kafka and Amazon SQS as pluggable backends, supports multiple use cases through namespaces, and scales independently through sharded deployments. The system provides durability guarantees while allowing teams to configure retry logic, delays, and targets without code changes.

   82
3. 3
   Article

   ByteByteGo·19w

   How DoorDash Moved to a Service Mesh to Handle 80M Requests/Second

   DoorDash experienced a platform-wide outage in 2021 caused by cascading failures in their microservices architecture. The payment service's high latency triggered retry storms that overwhelmed dependent services. This incident exposed inconsistent reliability patterns across their 1,000+ microservices. The engineering team responded by implementing a custom service mesh using Envoy as the data plane, rejecting both Istio (too complex) and Linkerd2 (insufficient features). They built a minimal control plane focused on adaptive concurrency, outlier detection, and traffic metrics. Starting with an MVP using file-based configuration and canary deployments, they gradually evolved to include zone-aware routing, header-based routing, and distributed tracing. The system now handles 80M requests/second across 2,000 Kubernetes nodes, with automated onboarding reducing migration time from days to under an hour.

   80
4. 4
   Article

   ByteByteGo·16w

   EP195: Common Network Protocols Every Engineer Should Know

   Network protocols form the foundation of internet communication, defining how data moves securely between systems. Transport protocols like TCP, UDP, and QUIC handle reliable and fast delivery. Application layer protocols including HTTP, TLS, DNS, SSH, and WebSocket enable web browsing, security, remote access, and real-time communication. Backend protocols like DHCP, NTP, and LDAP manage addressing, synchronization, and directory services. The guide covers 8 popular protocols in detail: FTP, TCP, UDP, HTTP, HTTP/3, HTTPS, SMTP, and WebSocket, explaining their specific roles in data transfer and communication.

   27