Which component is most essential to handle media file uploads in a scalable messaging system?
Think about where the media files themselves are kept and accessed.
The media storage service is critical to store and serve media files efficiently. Other components support messaging but do not handle media storage.
What is the best approach to efficiently deliver large media files to many users in a messaging app?
Consider how to reduce latency and server load when many users access the same media.
A CDN caches media files close to users, reducing latency and server load. Direct sending or no caching causes delays and high load.
Which storage format tradeoff is most important when designing media sharing for messages?
Focus on how media files are stored and accessed efficiently.
Storing media as blobs in databases can cause performance issues; object storage is optimized for large files and scalability.
What is the primary reason to store metadata (like file type, size, thumbnail) separately from media files?
Think about how apps show previews or lists of media without downloading full files.
Metadata allows the system to quickly show information and previews without loading large files, improving performance and user experience.
A messaging app expects 1 million users sharing an average of 5 media files per day. Each file averages 3 MB. What is the approximate monthly storage requirement in terabytes (TB)?
Calculate total daily data, then multiply by 30 days, convert MB to TB (1 TB = 1,000,000 MB).
Daily data = 1,000,000 users * 5 files * 3 MB = 15,000,000 MB = 15 TB/day. Monthly = 15 TB * 30 = 450 TB (option A).
