4 ms·
At the point where you're able to cache the exact HTML you're returning to the client, it's more efficient to do that in front of your node server than behind i
by sciurus 10y ago
At the point where you're able to cache the exact HTML you're returning to the client, it's more efficient to do that in front of your node server than behind it. A cache hit can avoid your application completely, which is a real boon for performance and scalability. You can run your own caching http proxy, like varnish, or use a CDN like Fastly.
- deleted 10y ago[deleted]
- ateevchopra 10y agoYes totally agree. Actually we are doing some experiments with that too. We chose redis for it's easier and simpler integration and highly programmably controls.