Three things you should never put in your database

Re:Three things you should never put in your database by otterley on Tuesday May 01, 2012 @07:15PM (#3916780)

There's nothing wrong with logging to a database, provided you adequately buffer the insertions to keep the underlying sync() rate reasonable.

I wouldn't recommend logging to the same database instance that's used to store customer data for both security and performance reasons, but that's no reason not to use a database for logging.

[ Parent | on HN ]

Re:Three things you should never put in your database by raverbashing on Tuesday May 01, 2012 @07:41PM (#3916850)

True

I agree, what it should say is: never log to the main database, create a DB especially for it (preferably in an entire different file system/disk/machine)

And don't forget to set it to 'append only'

[ Parent | on HN ]

Re:Three things you should never put in your database by anthonyw on Tuesday May 01, 2012 @07:22PM (#3916801)

> "There's nothing wrong with logging to a database"

Indeed; MongoDB is quite often used for storing (structured) log data.

[ Parent | on HN ]