4 ms·
If those considerations matched my needs, AWS wouldn't look great because I don't want vendor lock in. That's why they're able to charge high prices-- once you
by nirvana 15y ago
If those considerations matched my needs, AWS wouldn't look great because I don't want vendor lock in. That's why they're able to charge high prices-- once you build on their platform, you can't easily migrate elsewhere.
I want to save time by not having to learn Amazon specific APIs (which seem to be terribly engineered, cause every time I want to throw a small project that way I find myself in a morass of poor documentation and way too complificated configurations.)
So, I see that really as an added cost.
- yummyfajitas 15y agoYou are only locked in if you use SimpleDB, dynamo, SQS, etc. Most of the standard infrastructure is quite replaceable. S3 can be easily replaced by more or less any file storage system (in Django it's 1 line of configuration), ELB can be replaced by any load balancer, ec2 by dedicated servers, etc. Admittedly, some code changes are required, but nothing architectural (e.g., S3BotoStorage -> RackspaceStorage in django). For anything bigger than a hobby project, it shouldn't be a major barrier.
- mark_l_watson 15y agoThe situation is different for me: almost every customer I have had in the last 3 or 4 years has at least partially used AWS so I have already gone through the learning curve. Your point on vendor lockin is certainly valid: if you really take advantage of AWS services, you are locked in without a porting effort (like AppEngine).