Design a Scalable Social Media Feed System (Twitter/X)

Scalable Photo Sharing Newsfeed Design

Design a highly scalable photo-sharing platform similar to Instagram. The system must support hundreds of millions of users who can upload photos, follow others, and view a chronologically ordered newsfeed. Focus specifically on the architectural challenges of feed generation at scale, handling 'celebrity' accounts with millions of followers, and ensuring low-latency media delivery under high global traffic.

S3RedisKafkaCassandraCDNNoSQLZSetAPI GatewayPostgreSQLJWT

00

Scalable Social Media Photo Sharing Service

Design a mobile-first social photo-sharing application. The system must support photo uploads, a social graph (following/followers), and a personalized home feed showing recent content from followed users. Key challenges include handling high read-to-write ratios, managing the 'fan-out' of content to millions of followers, and ensuring low latency for global content delivery. Discuss trade-offs between push and pull models for feed generation and how to handle celebrity users with massive follower counts.

PostgreSQLRedisS3CloudFrontRabbitMQKubernetesJWTCDN

00

Design a Scalable Social Media News Feed

Design a news feed system similar to Meta (Facebook) that supports 1 billion daily active users. The system must allow users to post updates, follow others, and view a personalized feed of content from their network in reverse-chronological order. Address the 'Celebrity Problem' (hot keys/fan-out spikes), ensure sub-200ms feed retrieval latency, and discuss the trade-offs between push-based (fan-out on write) and pull-based (fan-out on read) architectures. Detail how you would handle data consistency, social graph storage, and feed caching at scale.

CassandraRedisKafkaPostgreSQLCDNgRPCZSETBloom Filter

10

Design a Scalable News Feed System

Design the core architecture for a global social media news feed similar to Facebook or Instagram. The system must handle over 2 billion Daily Active Users (DAU). Key requirements include: supporting various media types (text, images, video), generating a personalized feed with low latency (<200ms), and managing the 'celebrity problem' (high-profile accounts with millions of followers). Explain your strategy for feed generation (push vs. pull), how you handle real-time interaction counters (likes/comments), and your data sharding approach to ensure high availability and horizontal scalability.

RedisKafkaPostgreSQLCassandraNeo4jFlinkCDNgRPCGraphQL

10

Design a High-Throughput Social Media Feed System

Design a social media platform similar to Twitter (X) that supports real-time tweet posting and home timeline generation for 300 million daily active users. The system must handle extreme write amplification caused by 'celebrity' accounts with millions of followers while maintaining sub-200ms read latency for the feed. Detail your strategy for the 'fan-out' process, storage sharding, and how you would balance consistency and availability during peak traffic events (e.g., major sporting events).

PostgreSQLRedisKafkaS3Snowflake IDCDNgRPCMicroservices

00

Scalable Social Media Feed Design

Design a high-scale social media platform similar to Instagram that allows users to upload photos, follow others, and view a real-time feed. The system must support 500 million daily active users and handle the 'celebrity problem' where certain accounts have millions of followers. Focus on the end-to-end architecture for media storage, metadata management, and the feed generation strategy (push vs. pull). Detail how you would ensure sub-second latency for feed retrieval and high availability for uploads.

PostgreSQLRedisS3KafkaCDNZSETJWTKubernetes

10

Scalable News Feed System

Design a news feed system similar to Facebook or Twitter. The system should support 300 million daily active users who can post updates and follow other users. Key challenges include maintaining low-latency feed retrieval (under 300ms) while handling the 'celebrity problem' where a single user might have millions of followers. Explain your strategy for data consistency, storage selection for the social graph, and your approach to the push-vs-pull fan-out trade-off.

KafkaRedisPostgreSQLCassandraZSETCDNgRPC

00

Scalable Microblogging Platform (Twitter-like)

Design a high-scale microblogging service that supports posting tweets, following users, and generating a real-time home timeline for 300 million daily active users. Address the challenges of massive read/write asymmetry, the 'celebrity fan-out' bottleneck, and ensure sub-second timeline latency under peak load while maintaining high system availability.

CassandraRedisKafkaS3KubernetesCDNgRPCZSET

01

Design a High-Scale Social Media Feed System

Design a global-scale social media platform similar to Twitter. The system must support posting short-form content, a following mechanism, and a chronological home timeline for 300 million daily active users. Focus specifically on the architectural trade-offs between push-based and pull-based feed delivery, handling celebrity accounts with massive follower counts, and ensuring sub-second latency for timeline retrieval under peak loads of 100,000+ QPS. Discuss how you would ensure high availability and eventual consistency in a multi-region deployment.

CassandraRedisKafkaS3PostgreSQLCDNKubernetesgRPC

00

Design a Professional Social Network Feed and Connection System

Design the core architecture for a professional networking platform like LinkedIn. The system must support user profiles, a bidirectional connection graph (1st and 2nd degree), and a highly scalable news feed. Focus on how you would handle a scale of 300 million daily active users, including strategies for feed generation (push vs. pull), handling high-profile 'power users', and ensuring low-latency retrieval of content from a user's professional network. Explain your choice of data stores for both profile metadata and the connection graph.

PostgreSQLNeo4jCassandraRedisKafkaElasticsearchJWTKubernetes

00

Scalable Microblogging Platform (Twitter)

Design a microblogging service similar to Twitter. The system must support posting short text updates, following other users, and viewing a real-time home timeline. Key challenges include handling high-volume read traffic (600k+ QPS), managing the 'fan-out' process for users with millions of followers, and ensuring sub-200ms latency for timeline retrieval. Address the trade-offs between push and pull models for timeline generation and define a storage strategy that scales to billions of tweets.

KafkaRedisCassandraPostgreSQLCDNS3Snowflake IDMicroservices

00

Scalable Social Media Feed System

Design a high-scale social media platform similar to Twitter. The system must handle millions of concurrent users posting updates and consuming a real-time chronological home feed. Key challenges include managing a massive social graph, handling 'celebrity' accounts with millions of followers without overwhelming the system (the fan-out problem), and ensuring sub-200ms timeline loading speeds. Discuss your choice of data storage, caching strategies, and how you would balance push vs. pull models for feed generation.

CassandraRedisKafkaPostgreSQLCDNKubernetesgRPCZSET

00

1