5 ms·

Just 2 days ago, a Linode employee was badmouthing AWS here on HN for being too expensive: https://news.ycombinator.com/item?id=10796094 https://news.ycombinat

by tshtf 11y ago

Just 2 days ago, a Linode employee was badmouthing AWS here on HN for being too expensive: https://news.ycombinator.com/item?id=10796094 https://news.ycombinator.com/item?id=10796094 A DDoS will be much more expensive to customers than choosing AWS over Linode (or an equivalent low-priced service). EC2 has been around since 2006, and never has had any issues resembling this.

scrollaway 11y ago
So you're comparing DDoS of a provider with everyday spending? I was contracted a few months ago to save a website crumbling under its bills. They had $11k / month in AWS bills. Brought it down to $600 / month by switching them to Linode with a more reasonable stack. Not everything is a nail. Sometimes the mistake is choosing AWS.
- cynicalkane 11y ago
  If you reduced their bill from $11k to $600, I'm betting AWS was not the main problem.
  - workitout 11y ago
    Given that the price calculators for Google Cloud, HP Cloud, Rackspace, etc are online, you can check for yourself. The key one is bandwidth cost for their services.
- eric_h 11y ago
  Amusingly, we moved our infrastructure from Linode to AWS and cut our bill roughly in half about a year ago.
  - scrollaway 11y ago
    That can happen as well of course. Like I said, not everything is a nail. Sometimes AWS is the wrong choice, sometimes it's the right choice. However a lot of people jump on AWS when they really should not.
    - eric_h 11y ago
      Agreed. We've got a moderately complex stack and on Linode the noisy neighbors problem caused us to require bigger boxes for certain layers than should really have been necessary. Honestly OpsWorks on AWS has been a fucking dream from an ops perspective - we've been able to fully automate basically everything. My only complaint about AWS is RDS: in order to squeeze maximum performance out of a database, you need to pay for IOPS, and boy do you pay. Fortunately, we only need a massive database instance a few weeks out of the year (our industry has some massive seasonal spikes), so it's not so bad.
deleted 11y ago
[deleted]

by tshtf 11y ago

scrollaway 11y ago

So you're comparing DDoS of a provider with everyday spending? I was contracted a few months ago to save a website crumbling under its bills. They had $11k / month in AWS bills. Brought it down to $600 / month by switching them to Linode with a more reasonable stack. Not everything is a nail. Sometimes the mistake is choosing AWS.

cynicalkane 11y ago
If you reduced their bill from $11k to $600, I'm betting AWS was not the main problem.
- workitout 11y ago
  Given that the price calculators for Google Cloud, HP Cloud, Rackspace, etc are online, you can check for yourself. The key one is bandwidth cost for their services.
eric_h 11y ago
Amusingly, we moved our infrastructure from Linode to AWS and cut our bill roughly in half about a year ago.
- scrollaway 11y ago
  That can happen as well of course. Like I said, not everything is a nail. Sometimes AWS is the wrong choice, sometimes it's the right choice. However a lot of people jump on AWS when they really should not.
  - eric_h 11y ago
    Agreed. We've got a moderately complex stack and on Linode the noisy neighbors problem caused us to require bigger boxes for certain layers than should really have been necessary. Honestly OpsWorks on AWS has been a fucking dream from an ops perspective - we've been able to fully automate basically everything. My only complaint about AWS is RDS: in order to squeeze maximum performance out of a database, you need to pay for IOPS, and boy do you pay. Fortunately, we only need a massive database instance a few weeks out of the year (our industry has some massive seasonal spikes), so it's not so bad.

deleted 11y ago

[deleted]