asp.net - Handling Images and file attachments in a Content Management System -


assumptions: microsoft stack (asp.net; sql server).

some content management systems handle user-generated content (images, file attachments) storing in file system. others store these items in end database.

some examples of both:

  • in filesystem: community server, graffiti cms
  • in database: microsoft sharepoint

i can see pros , cons of each approach.

in filesystem

  • lightweight
  • avoids bloating database
  • backup , restore potentially simpler

in database

  • all content in 1 repository (the database)
  • complete separation of concerns (content vs format)
  • easier deployment of web site (e.g. directly subversion repository)

what's best approach, , why? pros , cons of keeping user files in database? there approach?

i'm making question community wiki because subjective.

if using sql server 2008 or higher, can use filestream functionality best of both worlds. is, can access documents database (for queries, etc), still have access file via file system (using smb). more details here.

erick


Comments

Popular posts from this blog

ASP.NET/SQL find the element ID and update database -

jquery - appear modal windows bottom -

c++ - Compiling static TagLib 1.6.3 libraries for Windows -