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
Leeward Bound
@leewardbound
to avoid vendor lockin, IMHO just build for k8s-and-psql (or anything self-hostable) eg don't use dynamodb / lambda / etc aws and gcp are basically interchangable for this. i have 2 clusters on each. i use kubestack to build clusters, i could move any of them to another cloud provider (or baremetal) pretty quick.
2 replies
0 recast
3 reactions
adrienne
@adrienne
Is this your preferred approach? To build in a cloud agnostic way so you can run code anywhere?
1 reply
0 recast
1 reaction
Leeward Bound
@leewardbound
yeah, building for lambda/dynamo lets you use other people's "starter kits" that eliminate bootstrap times, but when AWS starts to charge 10k+ monthly for these services, you have to rewrite your app to leave. so i made my own "starter kit" incl k8s boilerplates, now i can start a new app that runs anywhere in <2h
0 reply
0 recast
0 reaction