3 ms·
You'd still need a cache, because you shouldn't be hitting the Twitter API every time you load a page. Then you might have to add a frontend cache to avoid havi
by icebraining 9y ago
You'd still need a cache, because you shouldn't be hitting the Twitter API every time you load a page. Then you might have to add a frontend cache to avoid having to regenerate the HTML every time. This solution allows you to avoid those two caches while being more efficient, since everything is only generated once.