This is just an ad.
FFS Hacker News, why is this front page?
Goodbye Google Cloud, Hello Digital Ocean
11–20 of 73 posts
Re: Goodbye Google Cloud, Hello Digital Ocean
#12More of a rant. There's time you need more flexibility. I'm serving 1.2MM requests per second from 3 GCP regions, managing instances and GKE clusters with terraform, and I cannot see how could I possibly set that up in a resilient fashion with DigitalOcean. I think DO is perfect for certain scale apps. You usually care about UI things mostly when you spin up couple servers; but when you operate hundreds of machines y…
so it seems in general you like GCP more than AWS? What is your opinion?
Re: Goodbye Google Cloud, Hello Digital Ocean
#13AWS, Azure and GCP instances are completely different to Linode, DO, Vultr, etc... With the first three you get dependable performance characteristics with minimal variation (excluding t* EC2), this is the exact thing you need to do reliable horizontal scaling. Linode and Vultr and DigitalOcean etc.. are great for the price point but if I'm CPU bound and about to scale the identical service to N boxes then it's a poo…
didn't get your last remark re bandwidth. If 1TB alone costs $90 at both GCP/AWS, how is 3TB + 2 CPU instance for $20 is a poor choice?
Re: Goodbye Google Cloud, Hello Digital Ocean
#14More of a rant. There's time you need more flexibility. I'm serving 1.2MM requests per second from 3 GCP regions, managing instances and GKE clusters with terraform, and I cannot see how could I possibly set that up in a resilient fashion with DigitalOcean. I think DO is perfect for certain scale apps. You usually care about UI things mostly when you spin up couple servers; but when you operate hundreds of machines y…
so it seems in general you like GCP more than AWS? What is your opinion?
Personally, not professionally, I like GCP more. Feedback cycle is (used to be) faster and it feels (used to feel) less enterprisey. I also liked the idea of a new player on the market, and wanted to make sure I vote for this diversity with dollars.
I think these days GCP and AWS are more or less on par. One thing I learned the hard way: invest time into calculating your expected cloud spend. Your use case, partners you integrate with, your audience. Those impact significantly on cloud pricing.
Re: Goodbye Google Cloud, Hello Digital Ocean
#15So he basically uses ec2 equivalent service and is complaining about the existence of other services.
Re: Goodbye Google Cloud, Hello Digital Ocean
#16Earlier quoted context omitted.
so it seems in general you like GCP more than AWS? What is your opinion?
Personally, not professionally, I like GCP more. Feedback cycle is (used to be) faster and it feels (used to feel) less enterprisey. I also liked the idea of a new player on the market, and wanted to make sure I vote for this diversity with dollars. I think these days GCP and AWS are more or less on par. One thing I learned the hard way: invest time into calculating your expected cloud spend. Your use case, partners…
"used to" - correct. my thoughts exactly 1 year ago: https://news.ycombinator.com/item?id=12235003
Re: Goodbye Google Cloud, Hello Digital Ocean
#17Earlier quoted context omitted.
so it seems in general you like GCP more than AWS? What is your opinion?
Personally, not professionally, I like GCP more. Feedback cycle is (used to be) faster and it feels (used to feel) less enterprisey. I also liked the idea of a new player on the market, and wanted to make sure I vote for this diversity with dollars. I think these days GCP and AWS are more or less on par. One thing I learned the hard way: invest time into calculating your expected cloud spend. Your use case, partners…
Also, some GCP folks are hanging out here and it's nice to have some insights into platform internals.
Re: Goodbye Google Cloud, Hello Digital Ocean
#18So he basically uses ec2 equivalent service and is complaining about the existence of other services.
yes. except DO bandwidth is $0.006 instead of $0.09/GB. am I paying extra for the sole existence of other services?
Re: Goodbye Google Cloud, Hello Digital Ocean
#19I think this is called maturity. GCP finally knows who the target customer is, and they're building features for them. DO has really nice and simple UI, but try to spin 5,000 servers and you will see what a hot mess it is.
GCP shines at a very large scale. For us, what makes the difference, is the spending predictability and massive discounts coming from running preemptible servers or simply committing to certain usage.
GCP is not as service rich as AWS, but most of the offered services are capable of withstanding incredible loads. In our case, while running on tens of thousands of mostly preemptible servers[0], we couldn't pull this off anywhere else (trust me, we've tried).
It's great to know which service works for your loads and make the best of it.
Re: Goodbye Google Cloud, Hello Digital Ocean
#20More of a rant. There's time you need more flexibility. I'm serving 1.2MM requests per second from 3 GCP regions, managing instances and GKE clusters with terraform, and I cannot see how could I possibly set that up in a resilient fashion with DigitalOcean. I think DO is perfect for certain scale apps. You usually care about UI things mostly when you spin up couple servers; but when you operate hundreds of machines y…
It's interesting that 130k connections/core is limiting to you. Care to share some more details? Are those websocket connections? If yes what do you use as your backend? Something custom?