AWS, 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?
Goodbye Google Cloud, Hello Digital Ocean
21–30 of 73 posts
Re: Goodbye Google Cloud, Hello Digital Ocean
#22[0]: https://www.digitalocean.com/community/questions/extra-bandw...
[1]: https://motherboard.vice.com/en_us/article/qkj35w/nra-compla...
Re: Goodbye Google Cloud, Hello Digital Ocean
#23Earlier quoted context omitted.
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?
You're getting 2 (or X) virtual cores - which means absolutely nothing and can vary from minute to mintue / hour to hour - Linode was even giving 8 virtual cores with the cheapest plan 2/3 years ago. Virtual cores on Linode/DO/Vultr are shared/contended, basically undefined in terms of lower bound performance - you are at the mercy of other tenants - and there's a lot more tenants in the building too (where number of…
Re: Goodbye Google Cloud, Hello Digital Ocean
#24Earlier quoted context omitted.
What do you do that serves 1.2mm requests / second? I don't disbelieve you, I'm just wondering what type of site that is since English Wikipedia is several orders of magnitude lower than that.
Ads, one of the most shitshow industries in the world.
Re: Goodbye Google Cloud, Hello Digital Ocean
#25More 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?
Ended up serving most of the traffic from n1-standard-16 or lower.
Re: Goodbye Google Cloud, Hello Digital Ocean
#26Earlier quoted context omitted.
You're getting 2 (or X) virtual cores - which means absolutely nothing and can vary from minute to mintue / hour to hour - Linode was even giving 8 virtual cores with the cheapest plan 2/3 years ago. Virtual cores on Linode/DO/Vultr are shared/contended, basically undefined in terms of lower bound performance - you are at the mercy of other tenants - and there's a lot more tenants in the building too (where number of…
Did you know that DigitalOcean provides "High CPU" droplets?
Re: Goodbye Google Cloud, Hello Digital Ocean
#27If Google’s own premium speedy network, anycast IP, global load balancing and security features bring no benefit to your web operations, then your math might be right.
If you need your LB to handle 10s of millions of HTTP/S requests per minute, then what other choices do you have other than Google?
F/W default “Everything within a project should allowed”? Sorry, but no way.
Not familiar with other DO capabilities, but cloud platform is not just about a VPS available throu REST API, it is way far beyond.
Re: Goodbye Google Cloud, Hello Digital Ocean
#28Re: Goodbye Google Cloud, Hello Digital Ocean
#29“Goodbye cloud, hello nice UI for VPS hosting”. If Google’s own premium speedy network, anycast IP, global load balancing and security features bring no benefit to your web operations, then your math might be right. If you need your LB to handle 10s of millions of HTTP/S requests per minute, then what other choices do you have other than Google? F/W default “Everything within a project should allowed”? Sorry, but no…
The same options every business that needed them has done for decades? Renting dedicated servers én masse, colocating, or running own datacenters? And doing this in multiple countries?
What I'd suggest for a start is renting dedicated servers or colocating in a few places (EU-Central, US east, US west), and running on that.
Dedicated servers, even with having to maintain them, are always cheaper than GCP. Even more so is the network traffic.
I've started with dedicated servers with a few European hosters myself where I'd be able to get servers and traffic for 40€ a month that would have cost me upwards of 14'000€ a month with GCP, AWS or Azure (180TB+ traffic per month, I don't have the exact numbers again, but I used each service's cost calculator for this). Sure, if I want high quality networking, I'd have to pay another 360€ per month extra with these hosters, but that's still cheap enough that it means I can basically run a 180TB/month serving service on a hobbyists budget.
Re: Goodbye Google Cloud, Hello Digital Ocean
#30I 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 usa…
For small projects, especially when I am paying the bills, it is difficult to beat OVH and DigitalOcean on costs.
That said, GCP is still my favorite provider, largely because using GCP makes me a little nostalgic for the time I worked as a contractor at Google - really enjoyed their infrastructure.