Elteto.net

A forum encounter with a user worried about committing to Pressflow emphasizes the importance of understanding the Drupal cross-compatibility.

This Drupal user is righfully concerned about installing a distribution that may not be there years down the road while Drupal sails on. It is absolutely understandable that no administrator wants to put his or her site in a situation when its driving technology is no longer supported in a few years. However, Pressflow is not as much a fork or a subset as a tweaked-up version of Drupal. It is exchangable with the same release version of Drupal (as an example, as soon as Drupal 6.15 was released, so was Pressflow 6.15). I used the car battery example of a more expensive, performance battery fitting the same way in a car as a cheaper one, serving the same purpose, with the performance battery having more juice. If the performance battery is no longer manufactured, and you need a new power source in your car, you can always put a different brand replacement in the same spot, although without the performance enhancements.

I successfully installed Pressflow by literally removing the Drupal core files, dropping the Pressflow core in the same spot. I did not even need to run update.php, though I did, just in case.

For organizations with not a lot of money to spend, there is no risk in implementing Pressflow on their site. The benefits of performance improvements for large sites are hard to ignore. True, Pressflow achieves some performance gains by not supporting older versions of PHP and MySQL, but with most hosting services (and Drupal modules) using PHP5 and MySQL 5.X, this will not be a problem for most organizations. On VPSs and dedicated servers, Pressflow supports caching systems, increasing site performance without large financial/technology investments.

Drupal add-ons will happily work with Pressflow, providing administrators with the power of modules, themes and all Drupal community resources.