0

Our system generates a lot of large XML files with the help of a background job. These are then processed by another background job to generate PDF. As of now we were storing everything over FTP with the paths being stored in a RDBMS. The user processes can then access the corresponding files (if they exist) and display.

During our team discussions for enhancing the system, a suggestion came up of storing these XMLs and PDFs over a NoSQL database. The arguments in support of NoSQL are:(we are not experts in NoSQL)

  • It would help us manage the updation and deletion of files better
  • The files can be easily backed up or replicated to multiple servers
  • Files should be faster to access than conventional FTP

Though we do not need any content filtering except for a identifier for file, I was wondering if this is a viable solution for replacing FTP and if so is MongoDB a good NoSQL database for this task.

Community
  • 1
  • 1
krammer
  • 2,598
  • 2
  • 25
  • 46

1 Answers1

3

having been there done that, I can say yes it is a good solution, all 3 of the arguments mentioned really stand, especially if your file size is <16Mbytes , if not you have to use gridfs which complicates things a little but not much.

Also if file size is small and you got enough memory you can use a covered query which can get you retrieval speeds comparable to redis

Community
  • 1
  • 1
nickmilon
  • 1,332
  • 1
  • 10
  • 9