I work as full stack developer, but never really spent time on Database designs. I had written code to retrieve data out of DB, but never ever created a schema from scratch. So, I thought of doing some side project to understand how database design involves.
I had decided to create a Resume Builder Application. Here are some of the features that I had thought about:
User can sign up to create his/her own resumes.
User can have multiple resumes. (only applicable for paid users, for free users only one resume)
Resume can be built from the UI (from available components) and user can save it as draft.
Resume can be published via url.
Published resumes stats like visitors count needs to be calculated.
User can delete the resume.
User can upload his/her pic.
User can add description about themselves.
Given all these, I have come up with this schema:
Here are the questions I have:
I have a general knowledge on RDBMS, so my schema targets databases like Oracle, MySql etc. But can we choose NoSql for this problem? If so why?
Is my schema correct? Does it work on large data with ease?
I thought of saving the resume layouts (layouts for each resume is decided by the user via say UI) in JSON format. Is it a good practice to use JSON datatypes?
ResumeData table serves to store the user data for each resume. Is it a good to have a separate table for the same?
If the answer for the first question is RDBMS, which database you will prefer? I had decided to use PostgreSql.
Thanks a lot for spending time on answering these questions.