Question

This is very much a noob question, so please bear with me.

Consider a web application with 100,000 users. Each user can create entries or blog posts, as you may call it. Assume each user has 100 entries. Would it be appropriate to store all the users in one table? (Meaning, a table with 100,000 rows?) and further have another table to store the entries made by each user.

Is this a bad design? What would be an efficient way to store all the information to facilitate quick access of the information?

Thanks for your time!

Answer 1

Having 100,000 rows is not a big number for a database table to handle – and separating the entries from the users is a good decision.

A simple structure would be something like:

User
  |
-----
| | |
Entry

User table

UserId
FullName
IsDeleted

Entry table

EntryId
UserId
EntryName
EntryContent
IsDeleted