3 ms·

> At least with building to k8s you can shift to another cloud provider if those problems end up too difficult to diagnose or fix. You're saying that the solut

> At least with building to k8s you can shift to another cloud provider if those problems end up too difficult to diagnose or fix. You're saying that the solution to k8s is complicated and hard to debug is to move to another cloud and hope that fixes it?

giantrobot 5y ago
> You're saying that the solution to k8s is complicated and hard to debug is to move to another cloud and hope that fixes it? Not in the slightest. I'm saying that building a platform against k8s let's you migrate between cloud providers because the cloud provider's system might be causing you problems. These problems are probably related to your platform's design and implementation which is causing an impedance mismatch with the cloud provider. This isn't helpful knowledge when you've only got four months of runway and fixing the platform or migrating from AWS would take six months or a year. It's not like switching a k8s-based system is trivial but it's easier than extracting a bunch of AWS-specific products from your platform.
- throwaway984393 5y ago
  It takes almost as much time and effort to move K8s as it does to reinvent one cloud implementation as another cloud implementation, and your system engineers still have to learn an entirely new system of IaaS/PaaS. You don't really save anything. The only thing K8s does for you is allow the developers' operation of the system to be the same after it's migrated.
  - pm90 5y ago
    > The only thing K8s does for you is allow the developers' operation of the system to be the same after it's migrated. I mean, yeah, that’s exactly what’s required to happen, and it’s a good thing because only your system engineers need to do most of the legwork. If you have a team of system engineers, you probably have a much bigger cohort of application engineers.

3 ms·

> At least with building to k8s you can shift to another cloud provider if those problems end up too difficult to diagnose or fix. You're saying that the solut

by SahAssar 5y ago

giantrobot 5y ago
> You're saying that the solution to k8s is complicated and hard to debug is to move to another cloud and hope that fixes it? Not in the slightest. I'm saying that building a platform against k8s let's you migrate between cloud providers because the cloud provider's system might be causing you problems. These problems are probably related to your platform's design and implementation which is causing an impedance mismatch with the cloud provider. This isn't helpful knowledge when you've only got four months of runway and fixing the platform or migrating from AWS would take six months or a year. It's not like switching a k8s-based system is trivial but it's easier than extracting a bunch of AWS-specific products from your platform.
- throwaway984393 5y ago
  It takes almost as much time and effort to move K8s as it does to reinvent one cloud implementation as another cloud implementation, and your system engineers still have to learn an entirely new system of IaaS/PaaS. You don't really save anything. The only thing K8s does for you is allow the developers' operation of the system to be the same after it's migrated.
  - pm90 5y ago
    > The only thing K8s does for you is allow the developers' operation of the system to be the same after it's migrated. I mean, yeah, that’s exactly what’s required to happen, and it’s a good thing because only your system engineers need to do most of the legwork. If you have a team of system engineers, you probably have a much bigger cohort of application engineers.