I've just added response caching to RESTfulCF. For successful, cacheable controller actions (GET requests only), the pre-rendered response is cached, so on the next request the controller action can be completely skipped.
An example application-scope cache is provided, but you shouldn't really use this for production. But as an example of how simple it is to enable response caching, you'd first need to add the cache instance in your Dispatcher:
Then, in the relevant Controller function, set that the response can be cached as follows:
That's it, you're done! All successful (200 status code) GET requests that get routed through this controller method will now be cached.
At White Label Dating we're using a memcached-based cache for storing reporting-related requests that can take a few seconds to pull together; see the RESTfulCF README file for details on creating your own cache.