1 views collected around this technical thread.
This article explains the core components and rendering pipeline of modern browser engines, compares them with 3D graphics engines, and discusses the evolution of both browser and graphics technologies, providing a comprehensive overview for front‑end and graphics developers.
Blink 1.0 is a lightweight 220 KB user‑space virtual machine that emulates x86‑64 Linux binaries, includes a built‑in JIT that can be twice as fast as Qemu for simple programs, and provides both command‑line and TUI debugging interfaces.
The article explains how Blink, Alibaba’s optimized Flink variant, uses dynamic tables and streaming‑SQL to ingest mobile telemetry via source tables, compute per‑minute metrics such as API success rates with tumbling windows, and write results to Alibaba Cloud Log Service, enabling real‑time dashboards and extensible use cases like fraud detection.
To meet Xianyu’s billion‑event‑per‑day real‑time analysis needs, the team built a petabyte‑scale warehouse using Hologres for storage and Alibaba‑enhanced Flink (Blink) for streaming, organized into ODS, DWD, DWS, ADS and DIM layers, enabling minute‑level aggregations, rapid anomaly detection, and instant product‑team insights.
Mahé, Xianyu’s real‑time product selection platform, uses Alibaba’s Blink stream engine to merge, evaluate roughly 300 rule‑based filters per item and emit only changed results, processing 1.4 billion daily messages at up to 50 k TPS through a four‑layer, stateful architecture.
The article explains what a browser really is, compares modern rendering and JavaScript engines, traces their evolution, warns about the risks of losing engine diversity, and argues that competition among multiple browsers is essential for a healthy web ecosystem.
To meet Double‑Eleven’s sub‑second, billion‑item feed demands, Alibaba’s Xianyu selection system evolved from a Solr‑based search pipeline through offline batch and PostgreSQL attempts to a Blink‑powered real‑time stream platform using Niagara’s low‑latency LSM storage, delivering high‑throughput, personalized product feeds.
This article analyzes why the browser engine's CPU usage does not converge to zero when a page becomes invisible or the app is backgrounded, presents a lightweight testing methodology, identifies dynamic‑element and Blink‑kernel bugs, and proposes concrete fixes that restore proper CPU convergence.