5 ms·

Another k8s distro that’s hard to administer is exactly what I wanted, definitely not what I used EKS in the first place (Real talk though, never heard of anyo

Another k8s distro that’s hard to administer is exactly what I wanted, definitely not what I used EKS in the first place (Real talk though, never heard of anyone at Amazon using EKS internally)

phamilton 5y ago
Internally do they use ECS?
- dastbe 5y ago
  (I used to work at aws) yes! specifically, quite a number of teams use fargate and its one of the 2-3 "obvious" ways to build services.
  - rejectedandsad 5y ago
    Literally everything is a Lambda nowadays it seems, so it seems like it's just Lambda -> ECS -> -> -> raw EC2 unless you're building directly on bare metal.
    - bopbeepboop 5y ago
      AWS is a global scale mainframe[1]. CDK programs are “programs” that run on the AWS mainframe[2]. Lambda is the most “basic” FFI from the world of AWS programs to the world of business logic. ECS/Docker does less automatically (eg, less permission management or environment management), but in exchange you get more open/generic “compute” for your own logic. EC2 is the freest, but again at the expense of even less automated security or environment management. There’s times for all of those — but considering it’s a 1 liner to make a folder into a Lambda in CDK programs, there’s a reason Lambda is popular. [1] https://www.morganclaypool.com/doi/10.2200/S00874ED3V01Y201809CAC046 https://www.morganclaypool.com/doi/10.2200/S00874ED3V01Y2018... [2] https://www.youtube.com/watch?v=AYYTrDaEwLs https://www.youtube.com/watch?v=AYYTrDaEwLs
    - bobnamob 5y ago
      Yeah, it really depends on where your service falls on the dependency chain. Services that Lambda depend on are heavily encouraged to use lower level options etc...
  - phamilton 5y ago
    Thanks! We've been running on ECS for 6 years now (basically within a few months of GA). When EKS launched we talked about maybe migrating over but ECS just feels more first class wrt cloudformation and stuff. It makes sense that internal teams rely on it.
jon-wood 5y ago
The big selling point for k8s vs ECS is that it (theoretically) allows you to lift and shift your cluster to another cloud provider without too much pain because load balancers/storage/etc sit behind an abstraction layer. When you are AWS that's not really something you're even going to consider, so you may as well build with the underlying primitives because its absolutely guaranteed no one is ever going to ask you to migrate to Google Cloud.
thelostpotato 5y ago
AWS SA here, I know several AWS Services that are now built on top of EKS or using EKS. One example is managed Apache Flink on Kinesis Analytics. "Kinesis Data Analytics deploys Apache Flink using Amazon EKS. Multiple Kubernetes pods are used in Amazon EKS for each AWS region across availability zones." https://docs.aws.amazon.com/kinesisanalytics/latest/java/disaster-recovery-resiliency.html https://docs.aws.amazon.com/kinesisanalytics/latest/java/dis...
JustinGarrison 5y ago
Amazon.com runs on EKS (and other services). You can see public customer references here https://aws.amazon.com/eks/customers/ https://aws.amazon.com/eks/customers/ ECS is 3 years older than EKS (2015 vs 2018) and a lot of AWS services launched (or planned to launch) during that time which is a very valid reason lots of customers picked ECS. (I work on the EKS team)

Another k8s distro that’s hard to administer is exactly what I wanted, definitely not what I used EKS in the first place (Real talk though, never heard of anyone at Amazon using EKS internally)

phamilton 5y ago

Internally do they use ECS?

dastbe 5y ago
(I used to work at aws) yes! specifically, quite a number of teams use fargate and its one of the 2-3 "obvious" ways to build services.
- rejectedandsad 5y ago
  Literally everything is a Lambda nowadays it seems, so it seems like it's just Lambda -> ECS -> -> -> raw EC2 unless you're building directly on bare metal.
  - bopbeepboop 5y ago
    AWS is a global scale mainframe[1]. CDK programs are “programs” that run on the AWS mainframe[2]. Lambda is the most “basic” FFI from the world of AWS programs to the world of business logic. ECS/Docker does less automatically (eg, less permission management or environment management), but in exchange you get more open/generic “compute” for your own logic. EC2 is the freest, but again at the expense of even less automated security or environment management. There’s times for all of those — but considering it’s a 1 liner to make a folder into a Lambda in CDK programs, there’s a reason Lambda is popular. [1] https://www.morganclaypool.com/doi/10.2200/S00874ED3V01Y201809CAC046 https://www.morganclaypool.com/doi/10.2200/S00874ED3V01Y2018... [2] https://www.youtube.com/watch?v=AYYTrDaEwLs https://www.youtube.com/watch?v=AYYTrDaEwLs
  - bobnamob 5y ago
    Yeah, it really depends on where your service falls on the dependency chain. Services that Lambda depend on are heavily encouraged to use lower level options etc...
- phamilton 5y ago
  Thanks! We've been running on ECS for 6 years now (basically within a few months of GA). When EKS launched we talked about maybe migrating over but ECS just feels more first class wrt cloudformation and stuff. It makes sense that internal teams rely on it.

jon-wood 5y ago

The big selling point for k8s vs ECS is that it (theoretically) allows you to lift and shift your cluster to another cloud provider without too much pain because load balancers/storage/etc sit behind an abstraction layer. When you are AWS that's not really something you're even going to consider, so you may as well build with the underlying primitives because its absolutely guaranteed no one is ever going to ask you to migrate to Google Cloud.

thelostpotato 5y ago

AWS SA here, I know several AWS Services that are now built on top of EKS or using EKS. One example is managed Apache Flink on Kinesis Analytics. "Kinesis Data Analytics deploys Apache Flink using Amazon EKS. Multiple Kubernetes pods are used in Amazon EKS for each AWS region across availability zones." https://docs.aws.amazon.com/kinesisanalytics/latest/java/disaster-recovery-resiliency.html https://docs.aws.amazon.com/kinesisanalytics/latest/java/dis...

JustinGarrison 5y ago

Amazon.com runs on EKS (and other services). You can see public customer references here https://aws.amazon.com/eks/customers/ https://aws.amazon.com/eks/customers/ ECS is 3 years older than EKS (2015 vs 2018) and a lot of AWS services launched (or planned to launch) during that time which is a very valid reason lots of customers picked ECS. (I work on the EKS team)