3 ms·
For heavy users of AWS services (not just EC2, but fancy SaaS/PaaS stuff) do you ever regret being locked in to a hosting provider? Does it restrict your abilit
by tootie 11y ago
For heavy users of AWS services (not just EC2, but fancy SaaS/PaaS stuff) do you ever regret being locked in to a hosting provider? Does it restrict your ability to develop locally? Have you been bitten by problems that you can't resolve because you don't own the product? Or do you pretty much just love it?
- xrstf 11y agoWe had cases where failing MySQL queries[1] would leave behind GigaBytes of garbage data that we (as users of Amazon's RDS) have to pay for and have no option of removing (besides killing the entire database and rebuilding a new one, which would cost us more than just living with the garbage). Having our own small EC2 instance with MySQL on it would have saved us quite a few hours of work/downtime. [1] Have a database of a few gigabytes of sizes, start an ``ALTER TABLE`` and wait until your pre-allocated disk space is filled up. The query dies and you just fucked yourself. Can happen unexpectedly: We tried to remove a non-existing index on a table and MySQL decided to FIRST copy the entire table and THEN report that there is no such index.
- gtaylor 11y agoFWIW, we absolutely loved it at the last place I worked. We were all too happy to let AWS host our Postgres instance (RDS), our static assets (S3 and CloudFront), and a bunch of other things. We weren't particularly locked in, either. We always had the option to run our own Postgres cluster (it just didn't make sense to spend the manpower on it for us). We could have hacked together our own CDN, but that wasn't our core business focus. For small companies with low manpower, build on the services and get things done fast and as well as possible. It may cost more upfront than doing it on your own, but you are probably going to come out ahead by minimizing your maintenance/security/administration surface area.
- ademarre 11y agoIt sounds like you were using relatively loosely coupled AWS services. RDS doesn't change your programming interface to the database, it just hosts it. If you needed to, you could switch to a non-RDS Postgres server with only a configuration change to your core application. Contrast this with using AWS DynamoDB, which would likely be a major overhaul if you needed to switch to something that could be used outside of AWS.
- tootie 11y agoHaha, I just posted a nearly identical reply to another commenct. We actually just selected SimpleDB over DynamoDB for a new project specifically because it supports JPA annotations instead of a custom SDK. We know we're going to have to transition to a private datacenter in the near future so we have to avoid lock-in. SimpleDB beat out RDS just on price.
- deleted 11y ago[deleted]
- NathanKP 11y ago> Do you ever regret being locked in to a hosting provider? > Does it restrict your ability to develop locally? No, we use Vagrant so that we can run our docker cluster either locally or on Amazon. We have stubbed alternatives for all AWS services, including SNS and SQS, allowing us to run the entire backend locally even without an internet connection. > Have you been bitten by problems that you can't resolve because you don't own the product? I'd say its kind of like coding in Ruby on Rails. If you are bit by a problem you can't resolve there is a high chance you are doing something wrong, or at least not the "one true way". Sometimes we have issues when exploring the edges of what is possible on the AWS ecosystem (we've been using the fresh-out-of-beta ECS, and running into a lot of limits there), but generally the basic stuff like S3, SNS, SQS, Elasticache, etc just works, and doesn't require any attention. It's just a working, hands off gear in your system. > Do you pretty much just love it? Sure. It's a lot better than racking physical hardware, and the deep integration between things like autoscaling groups, EC2, ELB, etc makes it easy to automate all the things. In the end the more our service is a machine that can run itself and repair itself (replacing its own instances as needed) the more I love it.
- eric_h 11y agoWe moved our whole stack from manually managed Linode instances to AWS Opsworks, Elasticache, RDS, etc. We are currently somewhat tied now to the AWS stack, though through a large collection of our own Chef scripts I imagine we could move to a manually setup chef setup ourselves. Largely we've been very pleased with AWS, but the black box nature of a number of products (particularly Elasticache and RDS), has caused us some minor grief. Also, the higher frequency of single instance failures (which our stack can handle pretty gracefully) is somewhat annoying. EDIT: We were also able to fairly significantly lower our bill with reserved instances while also significantly increasing our ability to handle peak capacity with AWS.
- tootie 11y agoI would think Elasticache and RDS would be the least of your worries since they're just fully managed versions of readily available software. You can always host your own Redis and SQL database. Something like DynamoDB would be way more complicated.
- tracker1 11y agoIt seems to me you could use any number of solutions for something similar to DynamoDB, though Cassandra would probably be my first choice.
- eric_h 11y agoReally the issue with Elasticache and RDS is that when they go down and fail over to new hardware, we have no idea what happened to cause an (admittedly brief) outage. Basically, we just open a support ticket and say "what happened", and they just say "oh, the machine failed and was rebooted"