3 ms·
I'm certified architect in both AWS and GCP and I prefer AWS. But it's possible it's because I learned it first. GCP is easier to start with for me, but become
by peakaboo 5y ago
I'm certified architect in both AWS and GCP and I prefer AWS. But it's possible it's because I learned it first.
GCP is easier to start with for me, but becomes annoying because it's missing things that I can do in aws.
For example, cloud run can't run docker containers that doesn't listen to a port. Just run it once and shut down like Fargate does in AWS.
They want people to use kubernetes which is more complex and has features a lot of people don't need ever. Fargate is simple and just works.
So I prefer AWS for reasons like that but I think GCP is easier to understand.
- avl999 5y ago> For example, cloud run can't run docker containers that doesn't listen to a port. Just run it once and shut down like Fargate does in AWS. I believe the Cloud Run team is working on it and it is in a private beta.
- nijave 5y agoHaving used GKE and EKS, I will say GKE is much simpler. Kubernetes is a powerful platform but you're right--it does have a lot of complexity and overhead. ECS and Fargate are pretty solid if you want to run fairly simple containers but it's still a bit annoying they don't have all the cross-service integrations that Lambda does (SNS/SQS invokation, Kafka, etc)