I know AWS isn't cool or sexy, but shit works.
It’s sad to see people rediscovering that GCP is not a serious product over and over again.
GCP Incidents
71–80 of 167 posts
Re: GCP Incidents
#72HOW TO CHOOSE A CLOUD PROVIDER * AWS: you will pay to have stuff work properly and you like having customer service * Azure: you hate yourself, you're running Windows or both * Google: you're cheap enough that basic functionality is an optional extra * Oracle: lol * Hetzner: cheap, good service, the finest pets in the world, no cattle
What about DO?
Please don't use AWS especially as a startup, you are going to kill yourself paying for compute, database and egress that is multiples times what you get from a vps. AWs is NOT cheap
Re: GCP Incidents
#73When they say moving are off Google Cloud services to bare metal, where do they plan to move?
Re: GCP Incidents
#74You should've migrated many months ago, if a cloud provider forces you to build your own networking or registry, you shouldn't use that cloud provider.
Well for folks building out cloud infrastructure, building your own networking stack and registry is a good way to achieve platform independence, without which you'll be left at a disadvantage and vulnerable to the whims of cloud providers who may or may not extend volume discounts, thus indirectly harming your ability to compete.
I would assume that the skills required for building your own network ist just as high as hosting your own hardware. But I don't have any data point, so just a wild guess.
Re: GCP Incidents
#75HOW TO CHOOSE A CLOUD PROVIDER * AWS: you will pay to have stuff work properly and you like having customer service * Azure: you hate yourself, you're running Windows or both * Google: you're cheap enough that basic functionality is an optional extra * Oracle: lol * Hetzner: cheap, good service, the finest pets in the world, no cattle
>Azure Or you have big enterprise customers that have a grudge against Amazon and Google and refuse to use anything else.
Re: GCP Incidents
#76HOW TO CHOOSE A CLOUD PROVIDER * AWS: you will pay to have stuff work properly and you like having customer service * Azure: you hate yourself, you're running Windows or both * Google: you're cheap enough that basic functionality is an optional extra * Oracle: lol * Hetzner: cheap, good service, the finest pets in the world, no cattle
You can absolutely do cattle with Hetzner. They support imaging and immutable infrastructure. They don't have a native auto scaling equivalent, but if you're using Kubernetes, they have a cluster autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster...
Hetzner Cloud's biggest gap for me right now is secure VMs: they don't support encrypted disks, UEFI, secure boot, or TPMs (and certainly nothing like AMD SEV). You can get a fat bare metal Ryzen box through Robot and DIY though.
Re: GCP Incidents
#77Re: GCP Incidents
#78You should've migrated many months ago, if a cloud provider forces you to build your own networking or registry, you shouldn't use that cloud provider.
That was the first thing that struck me, the 'workarounds' stagger belief, but they seem to be casually dropped in (?). If I were in a situation where my company was contemplating implementing building our own registry/network stack, then the benefits of using a cloud provider are gone, and I would have considered moving to another provider... not saying "I can fix him". This feels like a sunken cost perhaps that is…
Re: GCP Incidents
#79Earlier quoted context omitted.
I hear this over and over, but what is the alternative cross-platform stack for building rich local GUI apps? Qt?
I’d say Flutter, a GUI framework backed by Google and it’s open source. I’ve recently ported over a popular project called “llama.cpp” to Dart (language behind Flutter) and I’ve recently made YT video’s showing it running natively on macOS, Linux, Android, iOS, iPadOS and next up is Windows. The official Ubuntu installer is made with Flutter too nowadays. But to be fair, last time I tried QT was somewhere in 2018, it…
Re: GCP Incidents
#80This makes no sense. A machine restarted and you had catastrophic failure? VMs reboot time to time. But if you design your setup to completely destroy itself in this scenario, I don't think you will like a move to AWS, or god forbid, your own colo.