4 ms·
I'd do that too but it would be cached and updated hourly. Why hit the Twitter api on each request?
by homero 6y ago
I'd do that too but it would be cached and updated hourly. Why hit the Twitter api on each request?
- benbristow 6y agoYou could set the app up to call the Twitter API but cache the response in memory or something like Redis so you don't need any background jobs/file management etc.
- homero 6y agoI've used memcached a lot but there's also benefits to caching a JavaScript file for an hour at a CDN and removing all load from that request.