3 ms·
Lock-In is dead simple to avoid with AWS. Even with Lambda, which people tend to point to and say "lock-in!". Even now we've got lambdas running Docker containe
by staticassertion 6y ago
Lock-In is dead simple to avoid with AWS. Even with Lambda, which people tend to point to and say "lock-in!". Even now we've got lambdas running Docker containers.
It's a total boogeyman and I've never heard anyone care about it except on HN, where it comes up constantly.
- sangnoir 6y agoYou seem to be agreeing with parent comment, from where I stand. Lock-in may be simple to avoid, but not many people make any effort to avoid it ("There are many fools in business"). I mean, take a look at the number of companies/services that got knocked offline last week because AWS's us-east-1 was fucky: if they are "locked-in" to one AWS region, do you think they'd bother with decoupling from AWS tech in general?
- Spivak 6y agoSo there's a reason for this that is unfortunate but true. AWS outages make the news and customers treat them like natural disasters. We host a few services on AWS but the bulk of our stuff is on-prem. When AWS has issues none of our customers cared -- they were annoyed that they couldn't do their work but were otherwise totally understanding and none of the blowback fell on us. When one of our upstream ISPs had an outage and prevented some of customers from being able to reach us people were mad at us even after the explanation. AWS is enough of a household name that you can say sorry "AWS is down right now" and people will sympathize.
- YarickR2 6y agofirst , it is real. second, it is very much a concern. we're buying game studios, and, if their projects are using Amazon-specific technologies( gamelift, f.e) we know it's an uphill battle to profitability ; games are low margin enough to take hosting and bandwidth costs into account