This question might be deadly simple but I wanted to make sure I am going through the correct path and not making any simple and irrevertible mistakes.
My project will be based on messaging and it won't be as less-used as a side tool like in Twitter or Facebook (not that they are not used but it's not the key option presented to users)
I was wondering will a simple table design like;
- from (id)
- to (id)
- content (text)
- created_at (date)
- isRead (boolean)
will suffice because, even though it is planned to be a small project, I do not believe that all the messages should be stored in one table and for each user when they want to view their messaging history, I shouldn't be scanning the entire table to do so. I am thinking about how scalable would this structure be and how would I benefit using a NoSQL DB like mongoDB.