3 ms·
This has been a popular twitter shorthand to dunk on AWS, but it's a really stupid list. Yes, there is more than one (there are six [0]) - targeted at different
by deanCommie 5y ago
This has been a popular twitter shorthand to dunk on AWS, but it's a really stupid list. Yes, there is more than one (there are six [0]) - targeted at different skill levels (e.g. someone coming from Kubernetes is going to have different expectations than someone starting with no prior knowledge).
But...
#1 isn't a way to run containers it's a way to organize best practices of your container images across your organization. That's closer to a container registry than a way to run containers.
#4/5 aren't "ways to run containers" - they are explicitly ways NOT to run containers. Like yes, you can CHOOSE to bring a container to a native EC2 instance, but it's not really a way to run containers any more than an empty lot a "Way to build a house"
#9 isn't a way to run containers, it's a service that you can instead run in a container to test it locally. Basically the opposite of the indication.
#10 admits it's misusing a service. You can provide a container definition to build your services via CodeBuild. Hardly what people think about when they talk about running a container in the cloud.
#11/12 are exactly the same semantics as with the root services - just running in your local datacenter instead of AWS. Counting those as separate is like counting EC2 as different services for every instance types.
#13 Fargate isn't a different way to run a container - Fargate is still ECS. It's just ECS where instead of managing the EC2 instances underneath you let AWS do it for you. The container interactions are identical.
#14 is a CLI tool to help with building container images that then run on ECS
#15 is a CLI to interact with the existing services
#16 predates containers
People take Corey Quinn way too fucking seriously. He shitposts. He makes jokes. He speaks truth to power. Sure. But he's got his tongue firmly planted in his cheek the whole time but people then parrot the stuff he posts as if it's a genuine well-thought out criticism.
[0]
* ECS (The default container service)
* EKS (For Kubernetes customers)
* Lambda (Cloud Functions that you can model as containers)
* Lightsail (AWS's VPS offering)
* AppRunner (AWS's CloudRun)
* ROSA (Redhat OpenShift)
- mayli 5y ago> #4/5 aren't "ways to run containers" So it's now illegal to rent VM and run containers inside in 2021?
- oblio 5y agoI think the main idea is that you can run anything you want inside them, not just containers. AWS doesn't care or necessarily provide many conveniences for this use case, you have to roll your own. This list is used to make fun of AWS for having *too many* options, so it's completely silly to criticize them for offering general purpose computing and then turning around and saying: "You're making our lives complicated! I can run containers that way! It's too confusing!".
- QuinnyPig 5y agoCounterpoint, Corey Quinn is also incredibly good looking and once fought a small Australian mammal in hand-to-hand wombat.