Many people don’t think server side scripting is consider part of Web 2.0. But I do. The better you make your code, the easier it is to updating, the less prone it is to errors due to server changes, etc. It definitely needs to be remembered.
The most important part of Web 2.0 SSS (Server Side Scripting) is DRY. Don’t Repeat Yourself. If you use the same few lines of code in a script, put them into a function. That way if you need to update those few lines, it’ll be updated throughout the script.
Then theres OOP scripting. A lot of people don’t bother to learn this, but its really important. OOP can increase the organization in your script by a huge amount as well as its DRYness.
An MVC (Model View Controller) framework is also important. I’ve always called it MVCH, because helpers are important. In my opinion, there gods gift to DRY. But MVC(H) frameworks allow you to do things you could never do before. The ease of changing a part of a code is amazing. Ever try adding or removing a column in a MySQL table? You have to go throughout the entire script changing every MySQL query. With MVC(H), you just have to edit a line or two in the model, and you’re ready to go.
But these improvements come at a price. All of them (excluding DRY) increase CPU cycles and RAM needed to run the site. This is no problem if your on a VPS or dedicated server, but it has led to overcrowding on shared servers.
But, despite the disadvantages, Web 2.0 SSS is not something to be ignored. Cheers!