Apologies to @timbray for the delay on this. It's threading time!https://twitter.com/timbray/status/1104222202314948609 …
-
Show this thread
-
Since
@caseyf is described as "good people," I'll assume his math is right and he can use a calculator competently.1 reply 0 retweets 4 likesShow this thread -
The real pricing issue in the thread is AWS's bandwidth charges. And yes, they're a lot higher than I'd like to see.
1 reply 0 retweets 1 likeShow this thread -
The question as to 'does it make sense for
@caseyf to migrate to AWS` is almost impossible to answer without more information, but there are some things to consider.1 reply 0 retweets 2 likesShow this thread -
If you 1:1 migrate what's in a dedicated colo, it will be screamingly expensive for a few reasons.
1 reply 0 retweets 7 likesShow this thread -
Colo bandwidth is based on port speed, often on a 95th percentile basis. Figuring out the actual amount transferred (and not just externally--between services as well!) gets you closer to the actual number.
3 replies 0 retweets 4 likesShow this thread -
Replying to @QuinnyPig
When migrating from a dedicated colo, it's no worse to use just one availability zone; and at AWS the traffic between your own services in a zone will be free. So it's important to focus on the external anyway, and if a CDN like CloudFront can be/is used.
1 reply 0 retweets 0 likes -
Replying to @colmmacc
Well… sort of. The new VPC endpoint bandwidth + per-endpoint hourly charge change that up a bit if you’re not careful. So does Managed NAT gateway.
1 reply 0 retweets 1 like
Colos don't have VPC endpoints or Managed NAT though!
A like for like comparison is generally to replace each colo server with an EC2 instance (and colo-contract equivalent-term RIs) in the same zone. Even EBS is a luxury you don't have if you're coming from colo!
-
-
Replying to @colmmacc
Just for you I'm going to design the worst possible AWS architecture imaginable and send it to you. "What the hell do you call this pattern?!" "Production."
3 replies 0 retweets 10 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.