This lesson's interactive features are locked, please to keep using them

Cache Integration

It's time to make moving around the map feel a lot snappier. We'll use each request's URL as a cache key.

A lookup that finds data is a cache hit. A lookup that doesn't is a cache miss. On a hit, we can unmarshal the cached bytes into the same response struct we use for a network response. On a miss, we make the request and save the response bytes for next time.

Assignment

Create a cache once in your PokeAPI request layer and reuse it across requests. Use an interval long enough to navigate between pages, like 5 minutes.
Check the cache before making a request. On a hit, unmarshal the cached bytes and return the result without making an HTTP request.
On a miss, fetch and decode the response as before, then cache the bytes after the request and decoding succeed. Return an error for unsuccessful HTTP responses or invalid JSON instead of caching them.
Add temporary logging for cache hits and network requests. Run map three times, then mapb: the first three commands should fetch different pages, and mapb should reuse the second page. Check that the location names still print normally.
Temporarily shorten the interval, wait for the page to be reaped, and revisit it. Verify that it makes a new request, then restore the longer interval and remove the logging.

Run and submit the CLI tests from the root of the repo.