3 ms·

And what if Amazon feels like changing Fargate or charging differently or deprecating it or... Whats your strategy for that?

• sk5t 7y ago
  The fallback is to use something else less convenient--maybe k8s, nomad, some other provider's container-runner-load-balancer-thing.
• pjmlp 7y ago
  We think about it when it happens, if it ever happens. I have seen too many projects burn money with vendor independence abstraction layers that were never relevant in production.
• throwaway894345 7y ago
  Like others have said, cross that bridge if/when we get to it--there's no sense in incurring the Kubernetes cost now because one day we might have to switch to Kubernetes anyway. It's also worth noting that Fargate has actually gotten considerably cheaper since we started using it, probably because of the firecracker VM technology. I'm pretty happy with Fargate.
• russellendicott 7y ago
  I'm pretty sure AWS has a better track record than Google when it comes to keeping old crud alive for the benefit of its customers. In my experience AWS generally gives at least a year's notice before killing something or they offer something better that's easy to move to well in advance of killing the old. Hell, they _still_ support non-VPC accounts...