educative.io

Storing user-related tables in one database and all files related tables in another database

1. Vertical Partitioning: We can partition our database in such a way that we store tables related to one particular feature on one server. For example, we can store all the user-related tables in one database and all files/chunks related tables in another database.

what would the tables look like? does below make sense?

  • user table
    • id
    • name
    • create date
  • file table
    • id
    • name
    • create date
    • user id
  • chunk table
    • id
    • file id
    • block storage location