Question

I have a PHP application that calls web services APIs to get some objects before rendering a web page that incorporates those objects. In some cases these APIs are really slow (seconds) and that is not acceptable from a user experience point of view. Two things I know I can do…

1. Use ajax and make these calls in the background
2. Time out the call and degrade gracefully if it is taking too long

Neither is ideal, so I was thinking about using memcache (the PHP extension for memcached) to cache the object that I get from the 3rd party web service. The objects will be loaded many times by different users loading the same page, so this seems to make sense.

The objects are relatively small (~1k).

Does this sound like a reasonable approach? I know memcached was originally designed to alleviate database load, so I’m wondering whether there is a gotcha somewhere that I’m not seeing.

Thanks.

Answer 1

This is a perfectly legitimate use of memcache. It is not only for database load reduction, it is for caching and object storage in general. 🙂

Also note, PHP has two interfaces for memcached. Confusingly, they are named “memcache” and “memcached“. Read these to pick between the two:

• https://serverfault.com/questions/63383/memcache-vs-memcached
• http://code.google.com/p/memcached/wiki/PHPClientComparison