design noSQL database mongoose nodejs

Asked Feb 20 '18 at 18:18

Active Feb 20 '18 at 19:48

Viewed 222 times

I build booking appointments barbershop app in react native with node js mongoose. in short, each user can make an appointment to barber. each barber has some types of hair cuts types.

user - Appointment (many to many) -> should I need to add appointment array in user?

Appointment - users (many to many) -> ref: user_id.

Barber- Appointment (many to many)-> should I need to add appointment array in user?

Appointment - Barber(many to many) ref: barber_id

Barber- HairCut Types(many to many): ref: types array

that's my demo design

I would like to know if the db design looks right? do I need to save appointments array in user and barber also?

edited Feb 20 '18 at 19:48

asked Feb 20 '18 at 18:18

Manspof

My opinion. In doubt. I'd use a RDBMS. – danilo Feb 20 '18 at 19:54
why? this db not complex – Manspof Feb 20 '18 at 19:56
maybe you are right, If it's your business the time will says. – danilo Feb 20 '18 at 20:57
why do you think it's better way RDBMS? – Manspof Feb 20 '18 at 20:57
1

I don't know if rdbms i better, I know that rdbms is flexible. – danilo Feb 20 '18 at 21:04
The 2 questions you asked depend on the needs of your business, depends on how you'll develop your system. I think it's good to have in both, but you need to choose between embedded or reference. https://stackoverflow.com/questions/5373198/mongodb-relationships-embed-or-reference – danilo Feb 21 '18 at 13:11
I said it depends because adding relationship increases complexity and size of your database, but I think both are very cheap in this case. – danilo Feb 21 '18 at 13:15

design noSQL database mongoose nodejs

0 Answers0