In general, my question is, how many options are currently available to Drupal users for handling high traffic? I'm looking at www.cmsmatrix.org and don't know much about the technical details on this. But I'll ask the following anyways.
Is load balancing possible with Drupal even though the core may not explicitly make this option available? The javascript pop-up text on cmsmatrix seems to say that core must support this, in order for load balancing to be an option.
What about database replication? Is this already possible if one were using PostgreSQL with Drupal? In other words, if the database is capable of this, does it not depend on Drupal's core? Otherwise, could the core of a CMS provide this capability, though the database might not have it alone (MySQL?).
How useful is static content export in high traffic situations and what would it take to make this available as a Drupal option?
I see Drupal can throttle itself but shutting down features. That's fine as a back-up for emergencies, but I'm more interested in keeping functionality and content available under high loads.
Thanks for your indulgence. Handling ramped-up loads is a key criterion for me.
Several PHP CMSs have load-balancing and other features here, but they also use PHP4's inefficient OOP features (I read on Zend that PHP 5 has new implementation of OOP that is much more efficient). I guess the best situation would be to have a PHP 5 CMS (with or without OOP) with load balancing.