Wednesday at php|tek in Chicago, IL

I attended a number of great session today at php|tek in Chicago 2008. Thanks to all of the presenters. I'm on absolute information overload. My gross oversimplification of a couple of notes are listed below, all warrant further research:

• When implementing mod_rewrite rules enable the Rewrite Log for troubleshooting. For every incoming URI (depending on the error level) the log will contain the incoming URI and what if anything your mod_rewrite rule is doing to the string. Make sure to only use in development.
• Using the flag [R=301] you can use mod_rewrite to return a 301 permanent redirect header.
• For distributed apps consider specialized subdomains that serve discrete purposes. This can aid in the breakup of an application into discrete scalable modules.
• For an immediate boost in performance on one box, implement some version of the following: /var/www/webapp map to www.domain.com for serving application content (i.e. PHP scripts), /var/www/static map to static.domain.com for serving static content (i.e. Images, CSS, JS) as IE will open another pipe to retrieve this content.
• For scalablity in your models seperate read and write functions as this will serve in scalability for when your database scales. One "easy" database scalability model has one database for writes and one or more for reads. By seperating your model upfront you allow for the before mentioned scalability.
• Not using AutoIncrement in your apps will make scalability to a Master-Master set-up less painful. Master-Master with AutoIncrements introduces some serious application issues.

This slides will be posted to this location when they become available.