A problem in almost all systems when dealing with caching and composite pages is to invalidate the cache for a page when a related entity is update. In this post we'll look at how you could handle this manually in Piranha CMS.
In Piranha CMS all pages are cached server side, as well as leveraging browser cache on the client side. This is of course to minimize the processing needed and to keep the site as fast and efficient as possible. When a page is updated in the manager interface the page_last_published date is updated and the server cache for that particular page is invalidated causing all subsequent request to get the latest version of the page.