4 ms·
I guess if you consider k8s to be it's own ecosystem and then frame the first two points as just a consequence of the ecosystem being inherently portable then I
by jpgvm 3y ago
I guess if you consider k8s to be it's own ecosystem and then frame the first two points as just a consequence of the ecosystem being inherently portable then I guess so?
IMO though compatibility and skill transferability (which speaks mostly to adoption rate) are separate things.
- acdha 3y agoDefinitely separate things - I just view them as part of the larger question of where you fall on the spectrum of how much you are outsourcing to your cloud provider. Another way of approaching it: would the cost of porting, say, an app which uses Lambda/SQS/SNS to GCP/cloud functions/PubSub be greater or lower than the cost of maintaining your own FaaS & queue/notification service on top of k8s? The answer isn’t fixed and will depend on things like your usage and staffing, and how complex your applications are, so I’d be most curious about how commonly people pick one versus the other and regret it due to some factor they didn’t anticipate.