Why I recommended ECS instead of Kubernetes to my latest customer
leanercloud.beehiiv.com
Why I recommended ECS instead of Kubernetes to my latest customer
1–10 of 126 posts
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#2> When looking at the cloud resources, we noticed many On-Demand EC2 instances with relatively low CPU utilization, which can be expected considering they don't have customers yet.
As a software consultant myself, I'd probably stop the conversation right there and ask why they are building such a robust distributed system — SQS, SNS, etc — without any customers. Still want to be deployed in AWS? Toss the damn app on a single EC2 instance...
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#3> When looking at the cloud resources, we noticed many On-Demand EC2 instances with relatively low CPU utilization, which can be expected considering they don't have customers yet. As a software consultant myself, I'd probably stop the conversation right there and ask why they are building such a robust distributed system — SQS, SNS, etc — without any customers. Still want to be deployed in AWS? Toss the damn app on…
Exactly. Worry about scaling when scaling is in the horizon
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#4> When looking at the cloud resources, we noticed many On-Demand EC2 instances with relatively low CPU utilization, which can be expected considering they don't have customers yet. As a software consultant myself, I'd probably stop the conversation right there and ask why they are building such a robust distributed system — SQS, SNS, etc — without any customers. Still want to be deployed in AWS? Toss the damn app on…
A single EC2 instance with SQLite as the database can get you pretty far.
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#5> When looking at the cloud resources, we noticed many On-Demand EC2 instances with relatively low CPU utilization, which can be expected considering they don't have customers yet. As a software consultant myself, I'd probably stop the conversation right there and ask why they are building such a robust distributed system — SQS, SNS, etc — without any customers. Still want to be deployed in AWS? Toss the damn app on…
[deleted]
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#6Interesting that the before and after figures are isomorphic as far as i can tell?
They introduced Terraform and dropped docker compose in favour of some Amazon proprietary container scheduler?
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#7More accurately: "Given using AWS as a requirement, I recommended ECS instead of K8s".
It's not really surprising that AWS's K8S setup isn't great, and their own implementation ties in more closely with other services they offer. It's lock-in. AWS provides just enough K8S to tick the box on a spec sheet, but have little incentive to go beyond that.
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#8ECS is hardly perfect, but I'd use it before EKS for a client who wasn't ready for that.
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#9The management of infrastructure via Terraform has a hidden engineering cost that should also be considered. Engineers can much more easily maintain, learn and introspect infrastructure via Kubernetes, despite its own complexity, given the immature, inconsistent and undeniably awkward qualities of the Terraform toolchain. Engineering time is expensive -- the morass of Terraform can easily quadruple engineering efforts.
Re: Why I recommended ECS instead of Kubernetes to my latest customer
#10> When looking at the cloud resources, we noticed many On-Demand EC2 instances with relatively low CPU utilization, which can be expected considering they don't have customers yet. As a software consultant myself, I'd probably stop the conversation right there and ask why they are building such a robust distributed system — SQS, SNS, etc — without any customers. Still want to be deployed in AWS? Toss the damn app on…
And in that case, why ec2, why not a more affordable provider?