Patching systems - how should you do this?
-
@dafyre said in Patching systems - how should you do this?:
@scottalanmiller said in Patching systems - how should you do this?:
@dafyre said in Patching systems - how should you do this?:
@scottalanmiller said in Patching systems - how should you do this?:
@dafyre said in Patching systems - how should you do this?:
@scottalanmiller -- how would you build a fault tolerant NFS server for something like this? Two Linux systems + DRBD?
You could do a two node this way. But for web servers with static files, why not just keep the files local and increase speed, simplify things and reduce complexity?
For systems that are static, sure. But what about something like Wordpress where files actually can be uploaded?
[I realize that may not be the world's greatest example, lol]
You would store those centrally, but not the main files. Often you would have dedicated image storage in a case that you were going to multi-node scale out web, not storing or serving from the application server. So typically tackled in a completely different way. Either through a CDN that you buy or build yourself.
Just look at ML, getting images to CDN is top priority from the very beginning.
I wasn't thinking about images, but, I get that idea. I was thinking more along the lines of user submitted uploads... but those could be sent into a database somewhere.
Those would be identical to images. Image, PDF, Word Doc... it's all the same to a CDN.
-
Common CDN that you might look at for this kind of thing is Amazon S3, Rackspace Cloudfiles, Backblaze B2, etc.
