Presentation: "Caching Hypermedia APIs"

Time: Wednesday 16:00 - 16:50

Location: Seacliff AB

Abstract: Cache invalidation in large systems can end up costing as much or more than not caching at all. But careful design of the shape and scope of your hypermedia resources can enable a system to rely on some of the natural behaviors that are built into the HTTP 1.1 protocol. Many real world examples will be used as we examine what works and what doesn't? How long can you cache things? How to make eTags cheaper? What can be cached and what can't? And why cache things at all?

Tim Stokes, Applications Architect at

 Tim  Stokes

Tim Stokes is the Applications Architect at, a not for profit organization that provides free resources for people to research their family tree. When Tim is not thinking about URIs he is talking about proxies and caching. Prior to FamilySearch, Tim worked in London and Sydney with a number of companies including BT, Citigroup, Royal and SunAlliance, Press Co, Prudential, GM Vauxhall, The London Stock Exchange, Qantas, AMP and Intuit Australia