3 ms·
You'll get fired for making a devastatingly bad call, and AWS could be one of those. It's difficult to work with, can be expensive if not used effectively, and
by astrodust 13y ago
You'll get fired for making a devastatingly bad call, and AWS could be one of those. It's difficult to work with, can be expensive if not used effectively, and exposes you to completely different kinds of risk than your team might be used to.
- samspenc 13y agoWe're a small company (30+ people) and been happily using AWS for several years now. We've found them price competitive for the same features - and they are really easy to use if you're looking for scale. A few reasons for why I think they're now the 600-pound gorilla in that space. ;)
- astrodust 13y agoI'm not saying it can't be done, but if you do it wrong you can really mess up your business.
- gaadd33 13y agoJust curious, do you just use EC2 and do you dynamically scale the number of machines you use frequently? All the math I've done for a constant number of servers/instances shows that unmanaged dedicated or colocated hardware comes out far ahead in price.
- PaulHoule 13y agoAnd you have the same risks if you pick any other cloud provider.
- astrodust 13y agoAWS has different risks. Many, such as Linode, will bend over backwards to fix your systems if they've suffered a hardware failure or data corruption issue. In using them for six years, with 50-60 instances at any given time, I've only permanently lost one instance. AWS is a purely do-it-yourself model, where hardware will blow up from time to time and data will get lost. Any and all infrastructure on AWS is to be considered temporary. Safety only comes with redundancy or a service layer like EngineYard that handles durability and persistence for you using their tooling. In three years of using raw AWS and hosting about a dozen instances, I permanently lost six instances, had several others corrupted and rendered unusable. You need to be prepared for parts their infrastructure to completely evaporate at any given time. Everything has to be persisted to S3 and off-site relentlessly. As much as it's true that you need backups for any provider, it's especially true for raw AWS. You're a tiny boat in a big ocean of trouble if you only have a few instances, no redundancy, and infrequent backups.