bedeviled mojo slop

There are many reasons why blojsom will never ever be backed by a database. I list a few of those reasons here because in the past few days and just reading through different blogs, it seems that performance and stability of databased-backed web applications (namely blog software) had come under some scrutiny.

• blojsom takes a different architectural approach in that it uses the filesystem as its content database. This was part of the original zen and philosophy of blosxom on which blojsom is based.
• A blog entry from Russell where he says, "Anyone who's seen the MiniBlog code knows that it's a mess - a zillion MySQL queries, no connection pooling etc. This actually, hasn't been a problem. Until now."
• A recent entry from JavaBlogs, Who ate the threads? where I picked up on two different quotes ... "I tried the kill -QUIT trick on FreeRoller this afternoon after it locked up. Looking at the stack traces for Tomcat's 75 threads, I found that most were either waiting for database connections or involved reading cache entries from the disk." ... more entry ... "Those changes kept FreeRoller up for a much longer period of time, but did not fix the problem."
• There would not be enough hours in the day to justify why I chose Hibernate over Castor JDO or why I didn't just use Prevalayer

Again, for me personally, I have a different opinion, architecturally speaking, of how and where blojsom is going to get its content. It just seems that in the database-backed cases, a key piece of the architecture on which the software runs, has not been given the TLC it so rightly deserves.