Called it, five years ago: http://www.web2expo.com/webexny2009/public/schedule/detail/9... Run in multiple clouds from day one. Take the pain. It gives you flexibility. Basic vendor management 101.
This article mentions nothing about latency.
Migrating From AWS to FB
91–94 of 94 posts
Re: Migrating From AWS to FB
#92Earlier quoted context omitted.
I'm confused by this. S3 GET requests are the cheapest request type, and getting the images out would just cost you the bandwidth involved. Maybe you're mixing things up with Glacier?
GET Requests are cheap But I was thinking of bandwidth costs to get things out of S3 entirely and do a complete outmigration. But the prices there have come down quite a bit since I last checked.
Re: Migrating From AWS to FB
#93Earlier quoted context omitted.
I think it has more to do with the fact that there are a standard series of private IP blocks.
Right, but if everyone used IPv6 there would be no need to use non-routeable private IPs for anything, you could just use non-conflicting IPv6 addresses and not route them.
One downside of IPv6 on AWS is that the IPv6 tunneling protocol -- protocol number 41 -- is only available in VPCs. The EC2 classic network allows only 3 IP protocols -- TCP, UDP and ICMP -- to pass through it.
Re: Migrating From AWS to FB
#94Earlier quoted context omitted.
We're small, comparatively - 20-30 servers max - and we need to get in to VPC for a new cluster that requires static internal IPs. (Reboot an EC2 Classic instance and you may get a different 10.x address.) In any case, the migration is daunting even at our size, although our devops team size is 1. I do wish they had VPC when we started.
You could also just attach EIPs and use those, right?