by Mike » Thu Sep 10, 2009 10:47 am
Re: PHP code optimization
On Thu Sep 10, 2009 latha wrote:
> Eyeopener article to server side issues and sometimes as they say it is better to
> de normalize your database than to normalise.
I made a comment once on a presentation made by Cal Henderson, the developer who conceived of and designed Flickr. In the presentation he said:
"Database normalization is for sissies"
Cal Henderson found about about my comment and sent me an autographed copy of his book Building Scalable Websites
He attached a hand-written note to the inside cover, changing his rule of "Database normalization is for sissies" to:
"Normalize First, Then Selective De-Normalize"
This is a rule I follow very strictly. But that said, I have no fear of denormalizing a database structure if it makes sense. Our Wyseguyz team has just started making database schemas and design a part of our documentation and QA process - the reason being of course that database design can be very impactful on the performance of any application.
His book, by the way, is an excellent read.
Mike