Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a REST API where I would like to cache the JSON response of the index (GET /foo) and the read actions (GET /foo/1) to significantly increase the performance. When there is a POST or a PUT on a resource the cache entries for the index and read results need to be expired, so no old content is served.
Is this a scenario that’s best done with a Reverse proxy like Squid / Varnish or would you choose memcache(d)?
Using a reverse proxy that sits on the HTTP layer is more transparent. That means that it’s possible to see what’s going on over the wire. The bad thing is that few of these support caching authenticated responses, so their efficiency may drop to 0 if your resources require authentication. Reverse proxies also don’t usually automatically expire resource A (
/foo) when this completely unrelated resource B (/foo/1) is modified. That’s correct behaviour that you’d have to add to your solution somehow.Both of these problems can be solved if you use memcached, since it doesn’t have the transparency requirement.