|
|
|
|
|
|
by whakim
1102 days ago
|
|
|
As someone who hasn't used Porter, it would be awesome if you could follow up this oh-so-snarky response with some actual concrete information? * What is the "unwittingly massive" level of complexity that they took on? Sure, k8s is complicated, but isn't the promise of this platform that it abstracts away all of that complexity? After all, AWS is very complex but we don't say that Heroku users are unwittingly taking on huge amounts of complexity, do we? * Why the assumption that "little research was done if they chose EKS"? Perhaps the company is already using AWS for other stuff? Doesn't the promise of a managed platform mean that you don't actually have to deal with EKS or GKE directly? * Your alternative platform suggestions don't really take into account their stated reason(s) for switching off Heroku - optimizing for scaling and lack of devops knowledge. Fly.io or Render are awesome but I wouldn't choose them for a rapidly growing company as they're essentially straight replacements for Heroku. I'm a big fan of ECS but it certainly requires some devops know-how - you better be comfortable setting up the entire AWS networking stack or want to commit energy to learning. I don't know the right answer here but it seems very use case dependent. |
|
|