3 ms·
(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.
by 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 agoLiterally 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 agoAWS 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 agoYeah, 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 agoThanks! 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.