How Twitter’s Fan‑Out Timeline Architecture Scales Real‑Time Feeds
Explains Twitter’s fan‑out timeline architecture, how it scales reads, the hybrid approach for celebrity accounts, and the trade‑offs engineers must consider.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Explains Twitter’s fan‑out timeline architecture, how it scales reads, the hybrid approach for celebrity accounts, and the trade‑offs engineers must consider.
An architectural deep dive into the asynchronous routing of tag-based questions, focusing on decoupling submission from distribution to maintain high performance.
A concise walk‑through of LinkedIn’s People You May Know scoring model, complete with a worked example, trade‑offs, and practical steps for engineers building similar recommendation systems.
A decision guide to adding a Memcached tier in front of MySQL, based on Facebook's published caching architecture: options compared, trade-offs, and a validation setup.
Learn how to implement the Fan-out pattern to solve timeline scalability issues, moving from expensive database joins to pre-computed cached feeds.
Learn how KrakenJS uses a master-worker architecture to scale Node.js across multi-core CPUs, including state management strategies and operational verification.
Goal: Identify the real bottleneck before scaling Railway dashboards expose per‑service CPU, memory, and network usage. Before resizing an instance or refactoring code, you should confirm whether the application is throttled by CPU, memory pressure, or disk I/O. Trade‑off: Persistent Volume vs. Stateless Service Attaching a volume guarantees that files writt