C
ChUIMonster
Guest
"filesystem" per se isn't really the issue -- raw devices are a thing of the past so everything is on a "filesystem" of some sort. Mike probably meant to say "file storage". Auto-correct must have jumped in and ambushed him 
The issue is that general purpose file storage can be reasonably implemented on devices that are sometimes called "file servers" and which a certain vendor of very poorly performing devices refers to as "filers". These are "file oriented" use cases. The primary goal of optimization on these devices is usually to minimize cost. The first victim of cost optimization is performance. The next victim is reliability. Thus such devices are anathema to databases. Databases need filesystems that are on devices that are optimized for random reads and synchronous, unbuffered writes. These are sometimes referred to as "block oriented" devices.
Continue reading...
The issue is that general purpose file storage can be reasonably implemented on devices that are sometimes called "file servers" and which a certain vendor of very poorly performing devices refers to as "filers". These are "file oriented" use cases. The primary goal of optimization on these devices is usually to minimize cost. The first victim of cost optimization is performance. The next victim is reliability. Thus such devices are anathema to databases. Databases need filesystems that are on devices that are optimized for random reads and synchronous, unbuffered writes. These are sometimes referred to as "block oriented" devices.Continue reading...