This video is a comparison between the two biggest mechanisms to manage and scale microservices: Kubernetes vs AWS ECS. Subscribe to our RU-vid channel: / clickittech AWS Consulting: www.clickittec... #Kubernetes #AmazonECS
What is the best container orchestration platform? Amazon ECS or Amazon EKS? Learn the differences between these two platforms in our blog! www.clickittech.com/aws/amazon-ecs-vs-eks/
Kubernetes is free, it's open source as well as being developed by an independent (CNCF) foundation outside of direct Google control. Why can't you run Kubernetes on a single machine? Kubernetes has rolling-updates by default. AWS is a more established cloud, so perhaps if you're committed to their services already - you should consider ECS.
Hello Al, I would like to elaborate more on the part that you mentioned that Kubernetes CANT run on 1 single server.1- Running Kubernetes on PRODUCTION with 1 single server would be unacceptable, it is not a good practice. Please, guys, remember, don't run 1 single server with Kubernetes in production. 2- You can run 1 single server for dev, testing, etc with minukube. For Kubeadmin would be for prod. 3- Every cloud provider (Azure AKS/Amazon EKS) requires a master, control plane, and the worker nodes. So at least 2-3 servers/instances per environment. Even with Google Cloud launches 2 servers. 4- Imagine running Kubernetes in prod with minukube with one load balancer and one server? Not good, right... no high availability (HA). Hoping this clarified what I tried to describe why you should run Kubernetes on at least 2 servers. I just released a new paper about how to create a Multi tenant Architecture using Kubernetes/ECS, or serverless: www.clickittech.com/saas/multi-tenant-architecture/
I just got the same feeling. It was just focus running Kubernetes on AWS and comparing the pricing against ECS. The technology pro & cons where hardly missing.
You're wrong about the costs: AWS's integrations force developers to test their code/infrastructure with the cloud. These development costs add up, especially when you have regular developers who cant directly see the costs they are incurring. Their entire business model is based on vendor lock-in, and assumes that you overlook the operational costs - like security and testing! You're wrong again about the costs: As I understand it, AWS's ECS solution uses an EC2 instance to run its containers by using an "agent". Since EC2 already has a hypervisor built in (and I highly doubt that the 'agent' replaces the hypervisor, as that doesnt make sense), its most likely running 2 operating systems -- which is more than the one that standard containerization like kubernetes uses. It'd be great if AWS used less obscure language when they try to teach things -- its like they're trying to convince you logically by using their own made up words. Like they want to make your brain fart.
Yep... ECS gives you more time to focus on other things. Lower learning curve and a few other things. But Kubernetes is so powerful and it can be used for other custom or enterprise solutions.
