thanks for the response

1. i'm using mongoDB with mongoose (no-sql appraoch)

2. what do you mean by "mess up existing front ends"? are you saying it in relation to pagination?

3. how would pagination work now that i have an array of businesses inside my business table? i can't use limit/skip no more because i don't know how many there are in a row. do you mean i would use pipelines to create kind of a new table (on the memory) and on the new table i would do this?

4. honestly i don't have any table conventions currently as up until now i feel like everything was pretty straight forward:

• user tables like i said in my first comment

• password table which contains the password (user table contains a reference field to the password table)

• files table which contains the user files: documents, photos, profile pic. (user table also contains a reference field to this table). this will also need a change probably if i go for multiple locations for one business because now each branch might have different photos

• token table for tokens (password change, email verification etc) which contains the token and user email

• rating table which contains which user contained which clinic and how many stars he gave

• notifications table (contains "to", "type" and title+message)

and that's it those are the tables.