I have a web app which has users, forms, and volunteers signed up on those forms.
Currently I am using MongoDB and have it setup with a collection for admins, and a collection for forms with volunteers attached to the forms.
It is not very efficient because I have to render the forms on two pages, so I have form data attached to admins in the user collection, but repeated in the form collection so they can be rendered individually on the form page.
Currently I have one page which needs to render admins and forms, and then the form page which just renders a single form. I am trying to minimize queries, which is why I copied form data to the user objects (admin info is also attached to the form, keeping it to one query for each page).
Volunteer information is attached to the forms, so it is copied in both collections. Obviously this is a terrible waste of space. I'm hoping someone can help me re-design this and recommend whether to stick with NoSQL or move to MySQL/Postgres.
I do not have enough experience to know which is better for this specific setup, or how to set the schemas/architecture to be scalable.
Thank you very much for your time. Any advice is appreciated, including relevant resources that I clearly do not know about.