With the popularity of social networking, and the growing evidence which shows that personalised web experiences produce better Return On Investment, web publishing platforms are slowly making the shift from static publishing models (which generate HTML files) to dynamic publishing, which generates personalised updated pages when needed.

Amaxus has always adopted the dynamic publishing model, which has allowed us to mature the platform and create various sophisticated caching systems that significantly improve performance, such that almost static-publishing speeds can now be achieved.

Caching systems in Amaxus include:

• Code and Data Layer
  • APC - Amaxus and dependant PHP libraries are byte-code cached
  • Doctrine Query and Result - memory cached
  • Database Caching (e.g. MySQL Cache)
• Process Layer
  • Block Cache (aka Module Cache) - disk, memory or database
  • Template Cache (aka Page Cache)- disk, memory or database
  • Page Cache (aka Site Cache)- disk, memory or database
• Front End
  • Javascript - bundled, minified and gzipped
  • Thumbnail images - automatically generated to size, fully cachable
  • Asset cache - a primed cache typically generates less than 5 http requests per page (in total)