May 2025
Intermediate to advanced
270 pages
6h 55m
English
Performance in an API endpoint is all about measuring the data we are returning in the response. To better exemplify this, we will check another endpoint in our application, the one that returns the films owned by each store: api/v1/stores/:store_id/films. If you hit the endpoint now, you will get only the most basic data of the films owned by that store. For example, this is the response in api/v1/stores/1/films:
| | [ |
| | { |
| | id: 1, |
| | title: "La La Land" |
| | }, |
| | { |
| | id: 2, |
| | title: "Breathless" |
| | }, |
| | { |
| | id: 3, |
| | title: "Ordet" |
| | }, |
| | [...] |
| | ] |
Now, imagine the following use case: for each film in that particular store, we also want to see the history of rentals. In the UI of our future mobile app, there ...
Read now
Unlock full access