My website online for 5 months, and the database has grown to staggering 60MB of database because of story and wfsection. With the trend, 3 years later I could end up with 4GB of database? Is this okies? Is there anything I should do because just backup the 60MB database took 20 minutes using myslqdump already. Any expert advice please?
Thank you

i think database size is not very important and number of queries is always cause the problem ( over load server and ...)
also for backup your db read this faq:
Can I backup my database and site files automatically

wfsection has an admin preference called "database restore". Check if this is set to "yes". It stores the whole article in the database everytime you make a change. If you have it turned on, and you make lots of little changes, your database could become huge.

If that is where your problem is, you should have a huge xoopsPrefix_wfs_article_restore table. You can safely empty (not drop!) that table if you don't need to keep old copies of your wfsection articles.

I don't know the "story" module, they might have a similiar system as well.