You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently load data for each year from the Marvel API and cache it in redis for 24 hours. So there's not an easy way to query data for all years. We either:
call Marvel API search endpoint with query (depending on usage, this could cut off API access since we have limited requests per day)
load data for a certain range of years (e.g. 1970-1975) and do the filtering ourselves
Though option 2 would be somewhat unsatisfying for those who want a truly global search (as originally requested).
We would probably want to keep filtering for option 2 strictly server-side due to the amount of data required.
I wonder if having dedicated series pages would mitigate some of the need for this issue.
I reckon the easiest way to do this is to do one mega-API pull of all 55.000+ titles in the Marvel Database and cache them, then every day just check if any titles have been updated in the database and pull just them and update or add whatever changed. I actually did the mega pull earlier, its around 200 MB of JSON (and I didn’t get locked out despite doing around 6,000 calls in total). Thoughts?
From #14
The text was updated successfully, but these errors were encountered: