10 Useful articles about Database design

July 15, 2009

Database designing is always tricky no matter how expert you are on the subject. Unfortunately, most of the time developers just want to concentrate on the programming side of the websites and focus less on one of the most important components of the web: the database (actually, it IS the main component of the web).

Sure you can go ahead and start designing tables and filling them out with data, but carefully planned databases will help you a lot in the long run, especially when you want to grow your service. Here’s a nice article by Antonio Lupetti where he points out 10 useful articles about database design.

Source: http://woork.blogspot.com/2008/09/10-useful-articles-about-database.html

Design Patterns – Introduction

June 26, 2009

Originating from architectural design (as in design of buildings), when design patterns crossed over to computer programming in the 1980’s, only a small group of people using a language called “SmallTalk” were applying them. In 1995, a group of four authors released a book called “Design Patterns: Elements of Reusable Object-Oriented Software”.

The four authors where nicked the “Gang of Four”. SmallTalk, but also C++ where the languages applying design patterns at that time. It is still the most respected book on design patterns to this date. “Gang of Four” (abbr. GoF) is also commonly used to refer to the book, rather than the authors.

Soon after, ‘Gurus’ such as Martin Fowler started publishing their own works, perhaps most notably “Patterns of Enterprise Application Architecture” (abbr. PoEAA). By then, most books where using Java in their examples. The Java community has played a big part in the evolution of Design Patterns, not in the last place thanks to efforts from Alur et al. with their “J2EE Core Patterns”.

Source: http://www.phpfreaks.com/tutorial/design-patterns—introduction/page1

Decoupling models from the database: Data Access Object pattern in PHP

June 26, 2009

Nowadays it’s a quite common approach to have models that essentially just represent database tables, and may support saving the model instance right to the database. While the ActiveRecord pattern and things like Doctrine are useful, you may sometimes want to decouple the actual storage mechanism from the rest of the code.

This is where the Data Access Object pattern comes in. It’s a pattern which abstracts the details of the storage mechanism – be it a relational database, OO database, an XML file or whatever. The advantage of this is that you can easily implement different methods to persist objects without having to rewrite parts of your code.

I’m again going to use the programming language quiz game I wrote as an example. Since I initially wrote it to use Doctrine ORM directly, and both the old and new code are available, you can easily see how the code was improved.

Source: http://codeutopia.net/blog/2009/01/05/decoupling-models-from-the-database-data-access-object-pattern-in-php/