The Bakery Everything CakePHP

Caching elements in general has been discussed before on bakery and this article takes caching of an element to a higher level. This article explains how to cache elements individually for each user.

Cake's core cache helper is great, but the files it outputs are PHP files, so it will never be as fast as straight HTML files. This HTML Cache Helper writes out pure HTML, meaning the web server doesn’t have to touch PHP when a request is made.

By reading the title of this article you know something has gone horribly wrong. Which was the case earlier today when my development server crashed with our teams shared database on it. While we did have backups of most of the data a few of the tables and a couple smaller projects were not so lucky.

When you set up ACL with a bunch of groups with subgroups, you will end up with five or maybe more queries per request. When you have a lot of active users it might fry your database. This is a simple solution to get rid of all those queries.

Often we need to disable Cake's query caching for a single find statement or a sequence of related finds. This behavior provides a way to do that quickly.

ACL checks can be costly and would benefit from caching. One approach would be to use Cake's Caching system, as implemented in http://bakery.cakephp.org/articles/view/caching-acl-permissions-with-cachedaclcomponent. Presented here is a different approach, where the cache is stored using Session.

This tutorial is intended for cakers who intend to make a scalable web app. Being familiar with php.ini, memcached and sessions is recommended.