Basically, it works like this: Instead of accessing the local filesystem, you access GridFS (and the contained files within) via the MongoDB database driver.Īs for the OS: Usually, I would avoid mixing different OSes within a deployment, if at all possible. It uses the rather easy means of MongoDB to distribute data across many machines, a process which is called sharding. Scaling storage capacity can easily become a very expensive part of an application. Now your second instance can access the images, and even store new ones, but that puts all the images on one machine, which sooner or later will run out of disk space. But now here comes the problem: the second instance of your application would not have access to the images stored on the first instance – bad thing. Luckily, aside from the fact that you store the images in the local file system, you implemented the application in a way that you could easily put up another instance and distribute the load between them. Now, your application becomes the next big thing, you have tens of thousands of concurrent users and your single server simply can not handle that load any more. You fire up your server, save the images to the local machine in /home/server/app/uploads, the users use the application. Say you have a web application where people can upload images. Let us dissect the example in a bit more detail. On the need for data distribution and its intricacies
0 kommentar(er)
