NoSQL database json structure for an event booking system -


first time designing database nosql , wondering if following structure project?

{    "events":{       "e2017":{          "name":"event 2017",          "date":"1490567256550"       }    },    "eventsections":{       "e2017":{          "e2017-a":{             "name":"a",             "isfull":false,             "totalseats":40,             "bookedseats":20          }       }    },    "sectionseats":{       "e2017-a":{          "a1":{             "isbooked":true,             "bookedby":"$userid"          },          "a2":{             "isbooked":false,             "bookedby":false          }       }    },    "eventseatmap":{       "e2017-a":{          "x":10,          "y":10,          "r":0       }    } } 

basically, database should store events contains sections. every sections contains seats can either booked user or not booked. implement seatmap each event, therefore have store transform properties (rotations, postition in canvas) of sections well.

is design "correct" nosql db or have got wrong?


Comments

Popular posts from this blog

javascript - Clear button on addentry page doesn't work -

c# - Selenium Authentication Popup preventing driver close or quit -

tensorflow when input_data MNIST_data , zlib.error: Error -3 while decompressing: invalid block type -