HDFS and GridFS are two great technologies for distributed file saving but what are their differences? What type of problems fit better to each?
4 Answers
HDFS intended for batch processing (you're know, when you running a query that will read many of your files one-by-one), but really suck when you doing random access operations and it is pain in the neck to maintain it or even deploy (you're know, all of these Zookepers, Namenodes and so on). On the other hand GridFS is slower at batches, but not in the case when you do a lot of random accesses, but have a bigger storage overhead compared to HDFS.
I would say that you should use HDFS for analitycs and GridFS for backing web-site.

- 62,329
- 13
- 183
- 228
Use HDFS if you are using Hadoop and use GridFS if you are using MongoDB. Neither are that great for just storing random files. They are built to work with the analytic platform.

- 38,889
- 8
- 95
- 118
I would recommend to use GridFS, if you are going only store your files without any analytic and map-reduce jobs. It's easier to customize and maintain. I used for file hosting application. HFDS in this case is overkill.

- 5,831
- 3
- 35
- 45
GridFs is little slow vs other fs ... at first think about other FS like ceph ...
Distributed file system - Wikipedia, the free encyclopedia -> http://en.wikipedia.org/wiki/Distributed_file_system
i think HDFS is realy fs but GridfS is only database grid
at last use benchmark but hardly suggest something Distributed file system
- nginx-gridfs Benchmarking Raw Results | ypass.net -> http://www.ypass.net/solaris/nginx-gridfs-benchmarks/rawresults.php

- 4,812
- 2
- 35
- 50