While a forum that gets 1000 posts/day is quite active, a database that does an INSERT ever 80s is not even moving.
We always limited transactions for UPDATES and INSERTs that involved more than one table.
It was quite the learning experience since you do have to think of different ways of working with data. You get to learn very quickly the difference between what like to store vs. what you actually need to store to get a particular functionality. But that turned to being a boon in the end because we got a much simpler forum as a result. Fewer bells and whistles meant users focused on actual discussion and not ancillary, shiny bits and bobs.
EDIT: And that is without any app specific caching.
Backups were pretty easy. ;)
http://www.sqlite.org/famous.html
Now it's an embedded database, which is why leokun's comment is out of place. However you can absolutely drop a queue in front of it, for instance, and serve many "simultaneous" users for a purpose such as a web forum.