cloud

In the first half of my CDN blog , I talked a little about why I wanted to move my biggest website to leverage cloud delivery of content, and the broad strokes of how I planned to get started. This second half details more of the specifics of how I technically achieved the early days of that transition.

In my day job, we've been steadily moving into the cloud for a while now for all the same reasons everyone else does: it gives us less to maintain ourselves in terms of hardware, it allows us to distribute worldwide more efficiently, it saves us money in the long run, and so on. At home, though, it's a different story, though most of the goals are similar. So now that I have some working knowledge of using Amazon Web Services to create a content delivery network (more commonly known as CDN), I decided it was time to apply it to my largest and oldest hobby site too.

One of the first things I blogged about was my new-at-the-time Carbonite account , though I didn't actually write the post about the service per se , more about how their speeds were shockingly slow for my initial backup. I write about them again today because as of now, I've just finished a two-week-long process of encountering a data disaster and the slow road to recovery, and Carbonite will again be a factor (but again not the main thrust of the idea).

A backstory: long before NASes became a...