Currently, the party information is fetched from a .json file (dummy data). We want to create a route in services that pulls the party data from our database. This includes coordinates, title, description, price, etc. MongoDB would be a good choice. Once we have the data, we can either render all of it, or (extra credit) only render parties that are nearby (i.e. 10 mile radius).
This is an important feature because many other features stem from it -- the party creation form, stripe checkout, and ticketing system, to name a few.
Currently, the party information is fetched from a .json file (dummy data). We want to create a route in services that pulls the party data from our database. This includes coordinates, title, description, price, etc. MongoDB would be a good choice. Once we have the data, we can either render all of it, or (extra credit) only render parties that are nearby (i.e. 10 mile radius).
This is an important feature because many other features stem from it -- the party creation form, stripe checkout, and ticketing system, to name a few.