Was running this blog off an EC2 t2.micro instance. But had some heavy traffic yesterday, 4000 users over 1 day from reddit. Which made me feel forced into switching hosts as if I got that level of traffic again for 3 days it would drain the cpu credits and kill the server.
So I spent a couple silly hours debating wether to go with DigitalOcean or Linode. I’ve actually used both in the past before and both have been fine. I ended up going with Linode since their cheap $10 instance had better specs than EC2 or DigitalOcean, 2GB ram and a CPU that’s not credit limited and a 24GB SSD. Compared to DigitalOcean’s $10 droplet with 1GB ram/20GB SSD/1 CPU no credit limit vs EC2s $10 t2.micro with 1GB ram/cpu that’s credit limited and extra additional AWS fees for just about everything that we all know about…
The one pain point I forgot about the older VPS providers is that setting up your initial server requires a little configuration. I used a ‘stack script’ from linode to setup WordPress but still needed to do all the security config manually after that like setting up rsa key auth and firewall rules. My command line skills are a little rusty, probably cost me an hour or two. I was also blissfully unaware centos 7 changed so much, “why is my service command ‘redirecting’ to systemctl what’s going on?? I DON’T UNDERSTAND”. The hour was probably worth not having to worry about my server going down from too much load without having to pay Amazon another $10 every month.
Though I did stick with Amazon’s CloudFront for my CDN which seems cheap enough, only cost 31 cents for the last week with the traffic spike so I’m not complaining and it will only cost more when there’s more traffic so my sites ads more than make up for it. I’m not sure how it compares to other CDNs however. Also stuck with AWS CodeCommit for my private git repo hosting since it’s free for 5 users, which I can’t complain about:).