8 ms·

Not just physical devices. A lot of the Google stuff I have to use seems half-baked, unfinished or with crappy UI/UX. And Google Cloud is complete shit compared

by brango 9y ago

Not just physical devices. A lot of the Google stuff I have to use seems half-baked, unfinished or with crappy UI/UX. And Google Cloud is complete shit compared to AWS. I guess that's what happens when engineers lead a company. They'll never have the customer focus that has made Amazon dominant.

saas_co_de 9y ago
> Google Cloud is complete shit compared to AWS that is a bold statement. care to elaborate?
- brango 9y ago
  Well for a start you have to stop a GCE instance to add a new scope to it. So if your devs want to use a new API and you're running a massive production K8s cluster, you somehow have to stop your instances to add the new scope and otherwise mess around. Of course if you know this in advance you can plan to do blue-green deployments with K8s, but if you don't know that you won't architect for it and it'll bite you. Their authentication in general seems convoluted and complicated, their console is slow and useless (why aren't all the search results preloaded? I type in 'iam' and it takes several seconds for the results to appear). Oh, and also alpha K8s clusters will terminate after 30 days whether you like it or not (perhaps you're using a feature that's apparently stable but languishing in alpha - I'm looking at you, cronjob). There's a lack of services in general (an elasticache type service would be nice) and development seems to move glacially. Also, they seem to have multiple versions of SDKs, some with outstanding bugs that were reported years ago but are just closed or there are comments in the README that only critical bugs will be addressed. There's no indication which SDK to use where there are several versions. Oh, and if you only want to use one service in python, you have to install about 40 different packages because splitting them up is too difficult. We've had DFP buckets have their configs get screwed up so we mysteriously couldn't access them, logs stopped being delivered, etc. Apparently Google have such poor monitoring that we had to prompt them about these things which took too longer to get resolved. I could go on...
  - chusk3 9y ago
    Holy smokes I feel you on the cronjob thing. They just went to beta with it in k8s 1.8, so now I'm waiting for that to get stable on GKE. That plus a managed Redis/memcached would be all that I need right now.
  - stanley 9y ago
    An easy workaround for the scope issue is to set a custom service account when creating the instance (template). You can then modify the IAM roles for that service account without having to take the instance offline. Allow that service account to have full access to all APIs on the instance level, then fine-tune what's actually possible through IAM Roles.

by brango 9y ago

saas_co_de 9y ago

> Google Cloud is complete shit compared to AWS that is a bold statement. care to elaborate?

brango 9y ago
Well for a start you have to stop a GCE instance to add a new scope to it. So if your devs want to use a new API and you're running a massive production K8s cluster, you somehow have to stop your instances to add the new scope and otherwise mess around. Of course if you know this in advance you can plan to do blue-green deployments with K8s, but if you don't know that you won't architect for it and it'll bite you. Their authentication in general seems convoluted and complicated, their console is slow and useless (why aren't all the search results preloaded? I type in 'iam' and it takes several seconds for the results to appear). Oh, and also alpha K8s clusters will terminate after 30 days whether you like it or not (perhaps you're using a feature that's apparently stable but languishing in alpha - I'm looking at you, cronjob). There's a lack of services in general (an elasticache type service would be nice) and development seems to move glacially. Also, they seem to have multiple versions of SDKs, some with outstanding bugs that were reported years ago but are just closed or there are comments in the README that only critical bugs will be addressed. There's no indication which SDK to use where there are several versions. Oh, and if you only want to use one service in python, you have to install about 40 different packages because splitting them up is too difficult. We've had DFP buckets have their configs get screwed up so we mysteriously couldn't access them, logs stopped being delivered, etc. Apparently Google have such poor monitoring that we had to prompt them about these things which took too longer to get resolved. I could go on...
- chusk3 9y ago
  Holy smokes I feel you on the cronjob thing. They just went to beta with it in k8s 1.8, so now I'm waiting for that to get stable on GKE. That plus a managed Redis/memcached would be all that I need right now.
- stanley 9y ago
  An easy workaround for the scope issue is to set a custom service account when creating the instance (template). You can then modify the IAM roles for that service account without having to take the instance offline. Allow that service account to have full access to all APIs on the instance level, then fine-tune what's actually possible through IAM Roles.