adrienne
@adrienne
Anyone here ever been responsible for choosing a cloud provider for their entire organization? How did you choose between AWS, GCP, Azure or others? What considerations or factors guided your decision? Was avoiding vendor lock in part of the equation? How large was the org and what industry?
12 replies
2 recasts
11 reactions
Samuel ใ
@samuellhuber.eth
@futureartist and @leewardbound are perfect to answer that
1 reply
0 recast
1 reaction
Alex Loukissas ๐
@futureartist
Avoiding vendor lock-in is the final boss of premature optimization. I've used both AWS + GCP and they are both good. For k8s, GCP gives you a more "pure" version of k8s, while EKS is an amazon branded version. Both have a fast db offering (dynamodb and spanner).
1 reply
0 recast
0 reaction
adrienne
@adrienne
โFinal boss of premature optimizationโ meaning a useless and pointless exercise so early on in the lifecycle? Optimizing for something that wont matter for years down the line, but paying the cost in terms of additional effort, complexity, and underutilization today? Is that the gist?
1 reply
0 recast
0 reaction
Alex Loukissas ๐
@futureartist
Yes! In general going full-in on e.g. AWS and using AWS services all the way gives you (IMO) more benefits of being defensive. One-way door for sure, but neither is a bad choice. A good thing to have is vendor-independent infra as code (e.g. terraform or pulumi).
1 reply
0 recast
0 reaction
adrienne
@adrienne
Thx ๐ Iโm working on a paper for the Enterprise DevOps Journal to provide guidance for how to think about lock in when it comes to cloud. Our audience is US Government. These are helpful anecdotes
1 reply
0 recast
1 reaction
