Having used AWS in production for about 2 years, I can say that scaling in the cloud is hard to get right. Spikes of traffic and load are hard to scale with, especially if you're scaling down to just the right amount of instances to manage the current load. We try to keep 50% capacity free for such spikes. Speaking with AWS support, we can fix issues with limits and scaling elbs, in hours not weeks, so I haven't had the same experience as you in that respect. One thing I would suggest, is that you have 2 AWS accounts. One for dev and one for prod. This way you should be able to see the limits that you're hitting before you get to production, and can raise tickets to get them ammended.
GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
161–170 of 179 posts
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#162I've used AWS for a bit over 9 months now and it's quite terrible to be honest. I don't need it for anything professional and it's quite terrible for just some amateur hosting plus the immense fees if you somehow manage to get decent traffic together. Once my reserved instances run out I'll probably either check out GCE or DO, either seems to be a better option, though GCE seems to be more expensive. Anyways, the con…
Short version: NEVER use AWS if you're not in a professional environment. Try Digital Ocean. That should be easier for you. Here's an article from the same blog to help you choose a cloud provider: https://thehftguy.com/2016/06/08/choosing-a-cloud-provider-a...
Thanks a lot!
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#163God I hate any piece of writing that doesn't define its acronyms at least once. Google Compute Engine isn't popular enough that people should be expected to know immediately what it means.
This entire blog post is rife with other small issues. AWS support is not a 10% minimum at all! Developer Support is 3%.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#164Earlier quoted context omitted.
We couldn't even get them to approve 5k servers on AWS. We run everything in GCE.
That is hard to believe. Their case studies have organizations using thousands or tens of thousands of servers for scientific computing, etc.
Those studies always involve close coordination between the PMs in the Cloud org and the client.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#165Earlier quoted context omitted.
They are fools. I will build you 1k servers with 100g to AWS in 75 days. Your $1M estimate is 3X too high at 2c/GB. In two hours I'll save you $25k per month. In 6 months $300k/month. Either you are growing and should be investing in cost efficiency or you run a staid lifestyle business. Which is fine, but if you aren't growing, get off expensive cloud.
You've a good logic in this, but you don't have enough details about us to judge it properly. The gain would be much smaller than you think and we would lose a lot of freedom, which would slow us down.
I don't think it's worth continuing to argue. It's obvious you've done your research and built a real system that works, you don't have to continuously defend people who claim you can save 50% but don't understand why running an entire system means more than just miniizing the hardware cost.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#166Earlier quoted context omitted.
Various servers, i2 for Cassandra eats most of it. Application at various levels, multi region etc etc We too are hockey sticking but not ready to go to metal .... yet. Your reasons make sense. I would grow that team soon :)
We have some large servers, but not too many of them. We're running 32 core nodes that are holding our Postgres, but the majority is smaller.
We are a data company :)
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#167Earlier quoted context omitted.
We have some large servers, but not too many of them. We're running 32 core nodes that are holding our Postgres, but the majority is smaller.
We are a data company :)
I would claim we're also https://twitter.com/synopsi/status/811755523091480576
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#168Earlier quoted context omitted.
> I think you're being close minded to building out a 20-60 cabinet data-center to offload some of your workload. I'd say it's time to forget about the infrastructure. Should optimize the software and rewrite in C++ :D
We already have huge portion of the system in C/C++ ;)
[deleted]
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#169Earlier quoted context omitted.
There are many reasons why bare metal doesn't make much sense for us, at least at the moment. Here are couple: - we're very small team (13 people). We would never be able to manage this kind of infrastructure - we're growing incredibly fast. Just 6 months ago we were running on ~300 servers. We grew so quickly that we are now working with GCE's infrastructure planers to plan our resource needs - even we're not suffer…
Would you mind giving more details about what you run with those 25k servers? I'd worry about the time it takes to reconfigure these servers with ansible/salt. or the time it takes to kill/rebuild them from a system image. On a side note, the 4th competitor is IBM SoftLayer. It's different enough from the top 3 (Amazon, Google, Azure) to be a thing of its own.
> Founder of Pex [pex.com], a video analytics & rights management platform able to find and track online video content anywhere.
src: doh's HN profile.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#170I have serious trust issues with Google. Their history of discontinuing services, dismal support (even for a paid service), and neglect of bugs in SDKs/APIs - all three of which I have experienced first-hand - has left a long-term bitter taste. No doubt some individuals are fantastic, but the organisation as a whole gives me an enduring impression of being systematically arrogant and aloof. AWS by contrast have demon…
It seems to me that Google is highly siloed internally. The GCP team is very visible (they engage on HN and elsewhere), and GCP has excellent support. Very different from other parts of Google. I have problems with Google as a whole, but I have as much faith in their cloud as I have in AWS or Digitial Ocean (we currently use all three). The Kubernetes team is also highly engaged on Github (they also occasionally show…
Not to be too cynical but none of this is reassuring. It's making it sound like the moment that GCP stops being the underdog they'll stop being as helpful and courteous :)