Hey,
A while ago i wrote about a cache system for magedb called MageFlexibleCache. Back than i didn’t know (much) about the CakePHP library. There current stable release doesn’t have that many caching capabilities but there new alpha (around for a few months now) has caching capabilities for all the cache engines that i wanted to support under MageDB (APC, XCache and File cache. CakePHP even has 2 others) so i was just wondering why i would have to make my own if it’s already there and under free (MIT) license as well. So nothing prevents me from using that cache stuff of CakePHP (and perhaps some other files as well).
So the newly created MageFlexibleCache was fun while it lasted.. if i can use that CakePHP cache stuff than i will use that (even PHP 4 compatible!!).
Now you probably find this boring because you don’t give a **** about caching.. you just want MageDB up and running.
Well.. here is a small list of the advantages that it gives you when i use that cache stuff.
Advantages
1. The site will load a lot faster in general
2. Queries can be saved a lot as long as nothing changes (one change and the cache will be rebuild for that part of the page)
3. The user experience will be a lot better than in a script that’s not using caching at all
4. Your server is capable of handing more requests because it’s mostly serving precompiled web pages (nearly no php and mysql).
Disadvantages
1. The script is getting a lot more complicated so making modules/addons for it will be complicated as well.
2. MageDB is making use of Ajax and that could give a few irritating issues
I can’t think of more disadvantages that a user might see..
So all in all the caching capabilities are good for MageDB and will be used.
Now i’m off to work on the (Experimental) Karma Rating script.
btw MageDB is really making some good progress these days.
Cya next blog,
Mark.
