perf: reduce bandwidth cost for some resumes API endpoints

[xiaohanyu]

Description

Some resumes API endpoints do not really need to return pdf field as part of the response, which could drastically reduce the size and latency of response.

List of API endpoints that could be optimized:

• PATCH /resumes/:slug
• GET /resumes

[Optional] Possible Solutions

• another approach is to use graphql so frontend can choose which field it needs, however, this is overkill for now

Acceptance Criteria

• resumes API endpoints should not return pdf field when the pdf is not needed by frontend

Todo list

NA

[xiaohanyu]

Done.

Before optimization

• GET /resumes for 4 resumes, 733 KB, 211 ms, in local

• PATCH /resumes/:slug, 214 KB, 239 ms, in local

After optimization

• GET /resumes for 4 resumes, 6.7 KB, 129 ms, in local

• PATCH /resumes/:slug, 3.4 KB, 189 ms, in local

[xiaohanyu]

Deployed on production and here are some result.

Before optimization

• GET /resumes for 5 resumes, 267 KB, 2.10 s

• PATCH /resumes/:slug, 121 KB, 1.74 s

After optimization

• GET /resumes for 5 resumes, 3.9 KB, 0.97 s

• PATCH /resumes/:slug, 10.2 KB, 1.21 s