When it comes to choosing a framework, PHP developers are very much spoilt for choice. From Rails-alternatives, to .net-in-PHP attempts, beginner-oriented procedurals to full-on enterprise systems, and even those that let you code however you like, there’s bound to be a framework out there for you. Of course, if there isn’t, you can always take an existing one and modify it to suit your needs (although most are sufficiently extensible).
Wikipedia has probably the definitive list of major PHP frameworks, covering everything from CakePHP to Drupal to the Zend Framework, and includes a few notable yet less-known options. Of course, this doesn’t tell you much about them; the comparison table is a little more helpful, although it isn’t restricted to PHP-frameworks.
There are a few important features to look for in frameworks:
- MVC: the Model-View-Controller design pattern, one of the more popular patterns, and certainly an effective one. Many of the big OO frameworks use this, and it’s good for those new to framework-based development.
- Templating: a templating engine is pretty much standard, if only through the V in MVC, but make sure it’s there.
- Caching: save yourself writing your own caching system when you find yourself dugg or slashdotted.
- Form validation: one of the most common yet most frustrating features of building PHP web application, a framework that simplified form validation is invaluable.
- Inbuilt CMS: depending on what you’re building, having a CMS ready-built for your framework can be really useful. Drupal and Joomla both come with CMSs.
- Inbuilt auth: Many frameworks choose not to include authentication, but not having to write your own user authentication system is a fantastic time-saver for basic application development.
Beyond this, take a look at the options out there. If you’re familiar with Rails, take a look at CakePHP and CodeIgniter. If you’re more of a .net person, Prado might interest you. If you’re looking for a CMS that you can code on top of, take a look at Joomla. One website even has a feature-by-feature comparison, although beware of following it entirely, as it doesn’t really reflect the true power of each framework.
Of course, while you may be undecided on your choice of framework, one thing is certain: you should be using a framework, if only one you hacked together in a couple of hours. Most frameworks will help you code quicker and more consistently, code reuse is suddenly the drop-in-place approach it should be, and it’s always handy to be familiar with a dev shop’s adopted CMS when sending them your resume.
