Data retention and caching plans #6
Description
While Goodreads API provides all the data we need, I feel it is wise to implement some of our own data retention / caching policy for fast lookup, and also a plan to how the requests will be made.
Plan A
App requests book ---> Server fetches book details from Goodreads API and parses it ---> returns book details to app as well as caches the data
Pros
- Cache retention, fast lookup for next time search (books can be hashed by Goodreads ID / ISBN)
- Security
Cons
- Multiple request. User would have to wait twice the amount of time
Plan B
App requests book directly from Goodreads API ---> Parses data and stores it back to Server
Pros
- One request always, less time needed
Cons
- Developer key has to be distributed to all apps for it to work OR have to configure per client Oauth
- Less data retention as always first call goes to Goodreads
- Lack of Security (access control)