4 ms·
It's because you did the heavy lifting up front with how your application is designed and how your infra is provisioned (I'm guessing everything is terraformed
by jamsauceismad 3y ago
It's because you did the heavy lifting up front with how your application is designed and how your infra is provisioned (I'm guessing everything is terraformed or something?).
- sleepybrett 3y agoAlso a great unlock if you do the bulk of your work in kubernetes. Amazon is certainly doing some things in their kube implementation that will make moving suck more (karpenter, some of their other integrations) in an effort to be better and thus sticky... But it's still pretty easy to go from one kube cluster to another.
- vidarh 3y agoEverything in Docker containers + a service discovery layer (Consul on that particular case) will get you most of the way there as long as you don't get seduced into relying on cloud specific services.
- scarface74 3y agoAnd then you’re managing Consul clusters (been there done that).
- vidarh 3y agoI never found that a problem. Consul was robust when I used it.