Suppose I want a decent sized video to be sent to millions of users. I want to store the video once and pointer to it in every user. Is it OK in this case to use 2 different tables or should I somehow try to squeeze the video into 1 table under the 'senderuser'?
Table: Users RowID: UserId ColumnFamily: Videos Column: VideoId Table:Videos RowID: VideoId ColumnFamily: Content Option2: Table: Users RowID: UserId ColumnFamily: Videos Column: VideoId ColumnFamily: VideoContent (This would be stored only for the 'sender' userid) Column: VideoId My queries are per user. Then once a user lists the videos, he/she can click on the link and retrieve the actual contents of the video. Option1 seems natural to me coming from a RDBMS world, but for performance I guess 2 would be better? Any tips are appreciated. Thanks in advance.
