Connecting Backend to Frontend

[oliver-pham]

There are two approaches to this:

1. Fetch from REST API

Standard usage documentation

2. Fetch from GraphQL Server
   Usage documentation (e.g. how data & queries look like) is defined in schemas:

type User {
    userID: String
    first_name: String
    last_name: String
    email: String
    bio: String
    password: String
    dob: Date
    sex: String
    location: Location
    hobbies: [String]
    preference: Preference
    avatar: Image
    photo: [Image]
}

We can implement both, but with the time constraint, we should prioritize either of them.

REST API

Pros

1. No extra research/learning
2. (Add more items)

Cons

1. If a route is changed from the backend, frontend may also need to update the call to fetch data.
2. (Add more items)

GraphQL

Approved by: @tuanthanh2067 @hlavu @mqnguyen5 @oliver-pham

Pros

1. Changes in the backend won't break the frontend
2. Avoid over-fetching & under-fetching data
3. (Add more items)

Cons

1. As a new technology, both frontend & backend need time to learn & implement
2. (Add more items)

[oliver-pham]

Source: https://www.mobilelive.ca/blog/graphql-vs-rest-what-you-didnt-know/

[tuanthanh2067]

I'd prefer GraphQL as it's faster, and it's something new so we can learn while working with it.

[oliver-pham]

Since the majority has decided to go forward with GraphQL, we'll prioritize it over REST API (reference issue: #5)