Paul Rubin wrote: > It's been a long-time source of puzzlement to me why so many web sites > are so slow, and RDBMS overhead is an obvious candidate. So the rant > seems appropriate even in the case of web apps where clients can cause > db updates.
Indeed. Large portions of a lot of Web sites could actually be deployed statically, rather than hitting a database several times a page to retrieve stuff which changes once in a blue moon. Moreover, static page hosting is generally a lot cheaper than dynamic program hosting. On the subject of requiring an RDBMS, though, whilst there are various kinds of applications which benefit overwhelmingly from using such a system, my experience with Web frameworks that have such prerequisites suggests that new users either have to slog through the setup process and take it on trust that installing and/or configuring an RDBMS is a good and necessary thing, or they question the relevance of having to set such a thing up. Certainly, for general Web programming, every time I see some Web framework which just ploughs straight forward with the "and now you'll need to set up MySQL" catchphrase for "our simple Wiki application", I can't help feeling that today's letters are W, T and F. Paul -- http://mail.python.org/mailman/listinfo/python-list
