0 views collected around this technical thread.
This article explains how Douyin, TikTok, Baidu, Alibaba Cloud and Tencent operate self‑built data centers with terabit‑level outbound bandwidth, details ByteDance's server count growth from tens of thousands to hundreds of thousands, and describes the CDN technologies that enable billions of users to stream smoothly.
This article explains how Douyin (TikTok) and other major Chinese platforms achieve massive concurrent usage by operating data centers with hundreds of thousands of servers, employing terabit-level outbound bandwidth, dual‑link designs, CDN acceleration, and multi‑node load balancing, and provides estimates of server counts and bandwidth capacities.
The article explains ByteDance's enormous data‑center bandwidth, server counts, and CDN architecture that enable hundreds of millions of concurrent users on Douyin and TikTok, detailing estimates of total outbound capacity, multi‑link designs, and the role of cloud and IDC resources.
This article explains how to reduce bundle size and improve load speed of large micro‑frontend projects by sharing common dependencies through CDN externalization, using tools such as qiankun, vite‑plugin‑cdn‑import, and Rollup plugins for HTML generation.
The paper presents Bilibili’s multi‑layer CDN edge‑node scheduling system, which groups heterogeneous nodes by quality and price, uses cost‑aware and resource‑aware heuristics—including maximum‑flow regional borrowing and contextual‑bandit utilization prediction—to allocate bandwidth per business, achieving a 43 % bandwidth reuse increase, 33 % coverage boost, and markedly lower stall rates.
The article explains how to build a custom Webpack plugin that uploads compiled static assets to a CDN, rewrites public‑path references to CDN URLs, and employs a hash‑based cache file to skip unchanged files, cutting build time from 40 seconds to 17 seconds in large projects.
Akamai will cease its CDN services in China on June 30 2026, offering migration partners like Tencent while explaining CDN fundamentals, benefits, components, and key terminology such as CNAME records, intelligent DNS, and origin protocols for readers planning a smooth transition.
This article presents a comprehensive multi‑CDN disaster‑recovery solution for frontend static resources, detailing the background, current issues, goals, SDK‑based architecture, monitoring and retry strategies, data‑reporting mechanisms, evaluation results, and future dynamic scheduling improvements.
The paper “Toward Timeliness‑Enhanced Loss Recovery for Large‑Scale Live Streaming” introduces AutoRec, an on‑off‑mode‑aware packet‑loss recovery mechanism implemented on QUIC that reduces average stall frequency by 11.4% and duration by 5.2% without client‑side changes, and validates its effectiveness in both test‑bed and real‑world CDN deployments.
This article explains the complete journey of a web request—from IP addressing, DNS resolution, and CDN acceleration, through TCP stream handling and message framing, to CGI/FastCGI execution, server model choices, and the evolution of data-layer architectures for scalable applications.
The team built a reusable low‑latency live‑streaming platform for the European Cup that replaces HLS with RTMP over QUIC, reuses VOD bandwidth, automates stream control, and cuts playback latency by 20 seconds while dramatically lowering bandwidth costs and delivering stable 1080p 50 fps HDR video.
This article explains the complete browser navigation flow from URL entry to page rendering and provides practical optimization strategies for DNS resolution, HTTP protocols, CDN usage, and front‑end resources such as HTML, CSS, JavaScript, images, and fonts to improve performance and user experience.
The article explains why static assets of a single‑page frontend application disappear after a container restart, analyzes the root cause, and presents a practical solution that stores assets on an external file server or CDN while keeping only index.html inside the container, thereby eliminating 404 errors caused by missing resources.
The article walks through every stage of a web request—from IPv4 addressing, NAT, and DNS resolution through CDN proximity and TCP stream handling, to HTTP framing, CGI versus FastCGI processing, stateless versus stateful server models, and finally database scaling techniques such as sharding and Redis caching.
This comprehensive guide explains how to identify and resolve slow web page performance by addressing hardware resources, network configuration, and both front‑end and back‑end optimizations such as server upgrades, CDN usage, HTTP/2, image compression, code minification, caching, and efficient database queries.
This guide outlines a comprehensive, step‑by‑step strategy for creating a highly available, secure, and scalable website—from buying and protecting multiple domains, configuring DNS and CDN, setting up image and database servers, to implementing monitoring, redundancy, high‑concurrency testing, and disaster‑recovery plans.
This article explains the concept of high concurrency, its key metrics, and presents four practical backend solutions—static/dynamic separation with CDN, read‑write separation using NoSQL and CQRS, various caching techniques, and lightweight read‑optimisation—to improve performance and scalability of distributed systems.
By splitting the main.dart.js bundle with deferred components, serving CanvasKit assets and Google fonts from a private CDN, and optionally using the HTML renderer during development, Flutter Web apps can cut their startup time by five to six seconds, achieving sub‑second load performance.
The article outlines how a VOD provider standardized its multi‑vendor CDN back‑source architecture by classifying videos as hot or cold, prioritizing fragment‑level pulls, throttling full‑file transfers, implementing real‑time monitoring, decoupling storage buckets, and adding OSIG authentication to reduce latency, bandwidth pressure, and security risks.
A June 2024 security breach compromised a popular JavaScript polyfill CDN, injecting malicious code that redirected over 100,000 sites, prompting warnings from Google and GitHub and highlighting best practices for protecting web applications from CDN‑based supply‑chain attacks.