4 ms·
The message of the cloud native software stack, most often built around Kubernetes, is that cloud portability enables you to avoid vendor lock-in. A look at th
by dankohn1 9y ago
The message of the cloud native software stack, most often built around Kubernetes, is that cloud portability enables you to avoid vendor lock-in.
A look at the stack: https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_v0.9.4_cncf.jpg https://raw.githubusercontent.com/cncf/landscape/master/land...
(Disclosure: I'm the executive director of CNCF and helped make this image.)
- deleted 9y ago[deleted]
- tracker1 9y agoAgreed, at the very least, anything I've made in the last year can be containerized and retargeted pretty easily from there.
- gaius 9y agoUsing cloud as a glorified hypervisor isn't really getting the benefits. To be cost effective you really do need to be using the value-added or layered features, and those are proprietary.
- dankohn1 9y agoI disagree (obviously). There are huge advantages to using the data stores from your cloud provider, but you can pick Postgres or similar options that avoid lock-in. If you use DynamoDB or Spanner, you can work to avoid non-portable features. Many other services like SNS can be replicated with software like NATS. That said, switching from one cloud to another will never be trivial, so it may be worth using some proprietary services up front if it gets you to market faster. The key thing is to have your eyes open about the choices you make, to ensure you have the ability to switch (or, perhaps more importantly, threaten to switch) in the future if you need to.
- gaius 9y agoSure, but if you restrict yourself to lowest-common-denominator features so you can migrate between Spanner and CosmosDB then you are paying for features you aren't using and are at a competitive disadvantage to those that can leverage them.