On May 20, 2004, at 2:45 PM, [EMAIL PROTECTED] wrote:
Another perspective on the subject of BLOB vs. Links.
Links are easier to implement and may be an OK way to start. However, a file system is really a crude database, and I emphasize "crude". It's not very good at handling high transaction rates, access from multiple machines, or volume.
If your application grows quickly and before you know it you have hundreds of folders with thousands of files in each - your file system will slow to a crawl. All the performance, security, and consistancy features developers have worked so hard to put into database engines don't or barely exist in file systems.
So - if you go the link approach - you'll be fine for a while, but when you see the directory structure starting to buckle - it might be time to give BLOBs another look.
Interesting. Would make sense that scale would affect the perceived and real limits and hassles of one method vs another, and flip-flop strengths & weaknesses. Thx.
-- greg willits
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
