This article details the evolution of Bilibili's dynamic feed system, outlining its business characteristics, multi-layer microservice architecture, caching strategies, and the transition from incremental pull to a hybrid push‑pull model to address scalability, latency, and data consistency challenges.
The article traces Bilibili’s Dynamic feed evolution from a legacy client‑server model to a four‑layer micro‑service architecture, detailing cache‑list storage, sharded relational and KV databases, and a push‑pull hybrid feed pipeline that balances massive write traffic, read efficiency, and future interest‑based recommendations.
This article explores the core concepts behind Twitter’s feed architecture, explaining how feeds and timelines are built from multiple lists, comparing push and pull notification models, discussing scalability constraints, and offering practical guidelines for choosing the right approach in large‑scale distributed systems.
This article examines the push and pull models used by micro‑blogging platforms such as Twitter and Sina Weibo, analyzes their scalability challenges, and proposes a time‑partitioned pull approach that reduces database load while maintaining fast feed retrieval for active users.
