The latest articles on DEV Community by Adam Dennis (@adamwdennis). https://dev.to/adamwdennis https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F279067%2F34d585b7-bf73-400b-b6c8-da842d7fac42.jpeg https://dev.to/adamwdennis en Adam Dennis Thu, 16 Dec 2021 14:23:47 +0000 https://dev.to/adamwdennis/graphql-vs-rest-a-response-time-performance-comparison-1ep8 https://dev.to/adamwdennis/graphql-vs-rest-a-response-time-performance-comparison-1ep8 <p>After creating a GraphQL API in a NestJS project with TypeORM, I've been trying my hardest to avoid adding REST API endpoints. Once I started implementing some basic auth via JWT's (w/access tokens &amp; refresh tokens), I wondered why it's not common to use GraphQL mutations for this purpose...</p> <p>I tried making everything the same, including the length of names for each endpoint/query. Here are my results:</p> <p>**Note: all GraphQL requests (queries and mutations) are POST requests.</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>API</th> <th>Type</th> <th>Avg Response Time</th> <th>Sample Response Times</th> </tr> </thead> <tbody> <tr> <td>REST</td> <td>GET</td> <td>0.329s</td> <td>0.280s, 0.261s, 0.316s, 0.472s, 0.314s</td> </tr> <tr> <td>REST</td> <td>POST</td> <td>0.561s</td> <td>0.690s, 0.454s, 0.479s, 0.814s, 0.369s</td> </tr> <tr> <td>GraphQL</td> <td>Query</td> <td>0.795s</td> <td>0.735s, 0.717s, 0.716s, 1.133s, 0.674s</td> </tr> <tr> <td>GraphQL</td> <td>Mutation</td> <td>0.711s</td> <td>0.713s, 0.753s, 0.684s, 0.703s, 0.700s</td> </tr> </tbody> </table></div> graphql nestjs rest api