Cloud drive versus cloud files (or should we not worry?)

The web application is in the process of moving from a standalone server to a couple of servers behind a load balancer and contains a 50-gigabyte directory of user-created data that is growing rapidly. In rackspace, the only way to add disk space dynamically is to double the RAM and monthly cost, which is optional. So for cloud files this is (if anyone else has a solution in mind?). Using JungleDisk, I can move the files to the cloud file container and mount the cloud container on both servers and create a symbolic link from the directories where the contents were on the mounted drive. This does not require code modification. Alternatively, I could interact directly with cloud files using their PHP API,but would that require big code changes (all the way?)? Is there an inherent problem in that case is easy to get out? I created a model, and it seems to work well, but usually something is missing.

Thanks Brandon

+5
source share
1 answer

I think that installing a disk makes a lot of sense for your scenario, but to be honest, I have not tried it with any kind of load. The good news is that you can always try a simple approach and then reorganize if it does not work under load. I would hope that Rackspace is taken into account and tested for this exact scenario, it seems logical to me.

Cloud Site vs Cloud Files. , , / - . , , , , .

RackSpace - . - , , . - , API , .

0

All Articles