![]() ![]() ![]() Today, when you upload a file to a service such as Google Drive, iCloud, Amazon S3 or a hosting grid, this file is automatically replicated in multiple servers and, very often, to multiple locations - so that when you try to access your documents while in Japan or the East Coast of the United States, your request is automatically routed to the closest pool of data that’s available. However, doing things the right way was not only costly and time consuming, but it required a fair amount of technical savvy (and we didn’t even get to discuss doing load balancing so that your files would still be available during high traffic situations). Now, if you were really fancy, you would deploy your files to different locations at once to ensure redundancy and availability, and to minimize the latency worldwide (that is, the amount of time between you request a file, and when you finally access it). And of course, things did happen to servers: hardware failures (it even seemed that hard disk drives (HDD) were just meant to break), crackers (if you ever had an account on a shared hosting, you just knew that every couple of months some foreign flag would appear on your site), and the always unintentional but clumsy overwriting or deletion of files (come on, we all did it). If you were fancy, you would make an additional backup of files, just in case something happened to that server. ![]() Not more than just a decade ago, when you needed to upload something to the internet, you would hire a hosting company to rent a certain amount of online space. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |