I bet one of the leading factors is the number of sites blocking the AWS servers. As a scraping service, the fact that Amazon makes all their public IPs known ( https://forums.aws.amazon.com/ann.jspa?annID=1701 ) is really inconvenient for anyone "crawling" the web. Rackspace also makes their list available, albeit incomplete ( http://www.rackspace.com/knowledge_center/article/cloud-site... ). As more websites setup…
We've actually never crawled out of Amazon (mostly because it was expensive to do so), so the crawl blocking stuff is unrelated, at least for us. As Sarah noted, it's really been costs, service, and support issues.
Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
51–60 of 137 posts
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#52For what many orgs need to do, a myriad of lesser-known VPS providers would be just fine, and be a fraction of the cost. But most people I've known don't investigate or educate themselves much - it's been a herd mentality towards AWS, irrespective of needs or costs (because often, it's not them paying - it's "the company"). Perhaps as a freelance consultant right now I take a sharper look at the costs involved - if a…
On a $50k project, how are you even dropping $10k on AWS? I've found a medium instance (~$100/mo) handles with ease 100k+ visitors/mo without breaking a sweat.
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#53To be clear, we haven't dumped AWS for short running stateless processing. We dynamically spin up spot instances as needed for all our stateless processing using AWS and other cloud services. At our current size our AWS bill will not be 7 million but closer to 500k-1 million a year. Not exactly pocket change. Some of the cost savings we are realizing is due to working with AWS as well on best practices. For our longe…
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#54For what many orgs need to do, a myriad of lesser-known VPS providers would be just fine, and be a fraction of the cost. But most people I've known don't investigate or educate themselves much - it's been a herd mentality towards AWS, irrespective of needs or costs (because often, it's not them paying - it's "the company"). Perhaps as a freelance consultant right now I take a sharper look at the costs involved - if a…
> if a client has, say, $50k to budget on a project, I really don't want $10k of that to go to hosting if it doesn't need to On a $50k project, how are you even dropping $10k on AWS? I've found a medium instance (~$100/mo) handles with ease 100k+ visitors/mo without breaking a sweat.
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#55To be clear, we haven't dumped AWS for short running stateless processing. We dynamically spin up spot instances as needed for all our stateless processing using AWS and other cloud services. At our current size our AWS bill will not be 7 million but closer to 500k-1 million a year. Not exactly pocket change. Some of the cost savings we are realizing is due to working with AWS as well on best practices. For our longe…
Thanks for the additional information. It was difficult to decipher your problems from the original article. I'm guessing the "no variability in load" processes are where AWS was the most unnecessary.
Paying for 70-100 hours of compute and having the server crash in the middle of calculating your predictive analytics not exactly all that bright either. So, we bought our own gear.
AWS works and worked with us pretty damn closely as we pulled apps out of the cloud.
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#56Did anyone else think "Moz" was short for Mozilla?
Not I, but I'm part of their demographic -- http://d2v4zi8pl64nxt.cloudfront.net/2013-in-review/52e9b643...
Or (more likely) is it that only 17% of people realized they do "marketing technology"?
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#57Earlier quoted context omitted.
> if a client has, say, $50k to budget on a project, I really don't want $10k of that to go to hosting if it doesn't need to On a $50k project, how are you even dropping $10k on AWS? I've found a medium instance (~$100/mo) handles with ease 100k+ visitors/mo without breaking a sweat.
depends on the work load, data size, computation needs, etc. measuring by "visitors per month" makes no sense.
I too find it difficult to think of a $40K project which is both likely to spend $10K at Amazon, and which can acquire equivalent resources (hardware, power, space, admin, etc.) for significantly under the same cost.
Not impossible, but real-world examples would be nice.
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#58I'd love to see some numbers on this though.
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#59Earlier quoted context omitted.
Thanks for the additional information. It was difficult to decipher your problems from the original article. I'm guessing the "no variability in load" processes are where AWS was the most unnecessary.
Yes! 95% of our services were running at AWS. Paying AWS for running our website is not a good use of money. Many cheaper ways to host a website. Paying for 70-100 hours of compute and having the server crash in the middle of calculating your predictive analytics not exactly all that bright either. So, we bought our own gear. AWS works and worked with us pretty damn closely as we pulled apps out of the cloud.
(Oh, and thanks for the information you've already shared - even if you can't answer my curiosity here…)
Re: Moz Dumps Amazon Web Services, Citing Expense and 'Lacking' Service
#60Earlier quoted context omitted.
I don't mean to claim otherwise, but I'd be interested to see what instances led to your observation.
As a simple example, if you have a moderate number of hosts in a single security group (e.g. 200+ hosts), you can expect to have intermittent communication problems between the nodes. They used to deny this was a problem. here's a source, since you're attacking and disbelieving everybody who doesn't love AWS: http://searchcloudcomputing.techtarget.com/news/2240203992/N...