July 22nd, 2006

Enterprise Bridge

No, really. No database.

Yes, Comic Con is going on. I have pictures. I've been too tired when I get home to upload anything. Cope.

This guy makes a solid point I've agreed with for a long time. Too much of what's on the web today is too tightly intertwined with databases and on-the-fly content generation. Far too many sites work like this: every time you hit a page, it fetches the content from a database, interprets and processes it, formats it, and delivers it to you. Far too often, that data has not changed. Maybe for hours, maybe for days. What a waste. Every page hit is far more CPU- and IO-intensive than it needs to be. If you need a database for storage, that's fine. Searchable archives, report generation, there's plenty enough good reasons to have one. But if most of your operation is really static, then the wiser course is to update static pages when you finish updating data. Make the operation simpler, and quit beating the crap out of your servers.