Anyone with a few Drupal sites under their belt knows that page caching is the key to a fast, easy-to-scale website, but what if the client is the front-end instead of a browser?

In this presentation, we'll look at best practices for caching when Drupal serves mostly as an API. Topics will include HTTP and REST caching best-practices, patterns for fine-grained invalidation of API responses, and how the front-end can work best when there's a proxy cache (e.g. Varnish) between it and Drupal.