Skip to content

Instantly share code, notes, and snippets.

@gavinlaking

gavinlaking/filesystems.md

Created August 5, 2012 17:30
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save gavinlaking/3266142 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save gavinlaking/3266142 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. gavinlaking created this gist Aug 5, 2012.
    7 changes: 7 additions & 0 deletions filesystems.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,7 @@
    If we should store assets on the filesystem rather than in the database because access is faster, then why are we not storing data on the filesystem rather than in a database? A database typically consists of a couple of files, one being the hunk of data itself, the others, supporting files like indicies.

    So, why not use the filesystem as it was designed: direct and flexible. Store our data using the right tool for the job; individual files storing discrete pieces of information. I can't think of anything that an off-the-shelf database ACIDically provides that our filesystems can not already do.

    Consistency may be lacking, from the respects of ensuring that a file is as it says (size, contents, etc), however, is it not the job of those wishing to store data to ensure it is correct before persistence? i.e garbage in, garbage out.

    What are your thoughts?