Generally CVEs/etc... aren't applied at the speed of light, so it's more or less ok to cache results from OSS Index for a period of time. This will prevent users from running into rate limiting on the service, and will also speed up the application in general.
What feature or behavior is this required for?
Prevents rate limiting
Speed up application
How could we solve this issue? (Not knowing is okay!)
I have literally no idea what to do here, so anyone with extensive R knowledge could likely lead us towards a key-value store of some sort where we could persist OSS Index responses. We'd cache them by coordinate with a TTL of 12 hours, more or less.
Anything else?
Have a BLAST!
cc @bhamail / @DarthHater / @brittanybelle / @adrianpowell / @csgillespie
Generally CVEs/etc... aren't applied at the speed of light, so it's more or less ok to cache results from OSS Index for a period of time. This will prevent users from running into rate limiting on the service, and will also speed up the application in general.
What feature or behavior is this required for?
Prevents rate limiting
Speed up application
How could we solve this issue? (Not knowing is okay!) I have literally no idea what to do here, so anyone with extensive R knowledge could likely lead us towards a key-value store of some sort where we could persist OSS Index responses. We'd cache them by coordinate with a TTL of 12 hours, more or less.
Anything else?
Have a BLAST!
cc @bhamail / @DarthHater / @brittanybelle / @adrianpowell / @csgillespie