home.social

#fargate — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fargate, aggregated by home.social.

fetched live
  1. Last year, I co-presented a "Serverless vs Kubernetes" talk with Davide de Paolis. I took the Kubernetes side, and I got lucky: if AWS had already announced managed instances, the serverless side would have had a much stronger hand.

    At that time, we ended in a tie: both serve different needs and different scenarios, with no clear winner.

    For years, every conference talk about compute ended the same way: "it depends on your workload." Lambda was brilliant but expensive at scale, Fargate was simple, but you couldn't pick your instance type, while EC2 gave you control, but your ops team aged 10 years maintaining it.

    Then Lambda Managed Instances, ECS Managed Instances, and EKS Auto Mode all dropped within months. The idea: EC2 economics with serverless operations. AWS handles provisioning, patching, and scaling. You choose the instance type, apply Savings Plans, and stop babysitting AMIs.

    We ran the numbers on a 50M requests/month workload. Standard Lambda: $343/month. ECS Managed Instances with a 1-year Savings Plan: $117. Same workload, same reliability, 66% cheaper.
    There's a catch, of course. Lambda Managed Instances scale on CPU utilization, not invocation rate. If traffic doubles in 5 minutes, expect throttling. And ECS Managed Instances pack multiple tasks per instance, so if you need Fargate-level isolation, you'll want single-task mode.

    You can find an in-depth comparison with cost breakdowns for steady and bursty traffic, plus a decision matrix for when to use what here: blog.besharp.it/when-serverles

  2. Kubernetes có thực sự cần thiết?

    Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.

    Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.

    #Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
    #CloudComputing #ECS #Fargate #CloudRun #Tech #Plat

  3. Kubernetes có thực sự cần thiết?

    Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.

    Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.

    #Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
    #CloudComputing #ECS #Fargate #CloudRun #Tech #Plat

  4. Kubernetes có thực sự cần thiết?

    Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.

    Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.

    #Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
    #CloudComputing #ECS #Fargate #CloudRun #Tech #Plat

  5. Kubernetes có thực sự cần thiết?

    Đối với hầu hết các workload phổ biến (API, services), các nền tảng của cloud như ECS/Fargate hay Cloud Run thường rẻ hơn, hiệu quả hơn và giảm gánh nặng vận hành.

    Hãy chọn Kubernetes khi bạn có nhu cầu rõ ràng: di động đa đám mây (multi-cloud), tùy chỉnh sâu, hoặc xây dựng platform nội bộ. Đừng chạy theo 'trend' mà hãy chọn giải pháp phù hợp nhất.

    #Kubernetes #DevOps #Cloud #SysAdmin #K8s #CôngNghệ #LậpTrình
    #CloudComputing #ECS #Fargate #CloudRun #Tech #Plat

  6. Thanks everyone who joined our Meetup yesterday!
    We had @runlevel0 talking about Running Elixir on AWS without Kubernetes (with a demo using AWS CDK and ECS Fargate), plus a Lightning Talk by Julian Köpke about his alchemy_pub project: https://github.com/j4nk3e/alchemy_pub

    Livestream recording: https://www.youtube.com/live/SUexJAYotKM

    #Munich #Meetup #Elixir #Phoenix #BEAM #AWS #CDK #Fargate
  7. Thanks everyone who joined our Meetup yesterday!
    We had @runlevel0 talking about Running Elixir on AWS without Kubernetes (with a demo using AWS CDK and ECS Fargate), plus a Lightning Talk by Julian Köpke about his alchemy_pub project: https://github.com/j4nk3e/alchemy_pub

    Livestream recording: https://www.youtube.com/live/SUexJAYotKM

    #Munich #Meetup #Elixir #Phoenix #BEAM #AWS #CDK #Fargate
  8. Decision Guide: AWS Fargate or AWS Lambda?

    AWS Fargate or AWS Lambda?

    https://docs.aws.amazon.com/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.html

    There is a new and very useful decision making guide for those wondering if AWS Fargate or AWS Lambda is the right kind of compute. It’s very thorough and well organized.

    Coincidentally, I was just having a discussion about this very topic with a customer yesterday. It’s always surprising to me what kinds of factors influence decisions like these. Popularity of a particular tech stack vs. simplicity and user experience are big ones. But, things like confusion around package size limits or potential edge case scaling issues once “we get tons of traffic” are the kind of thinking that very often lead us down a weird road.

    Hopefully this guide will help customers make sound decisions at the right moments in their dev cycles.

  9. Decision Guide: AWS Fargate or AWS Lambda?

    AWS Fargate or AWS Lambda?

    https://docs.aws.amazon.com/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.html

    There is a new and very useful decision making guide for those wondering if AWS Fargate or AWS Lambda is the right kind of compute. It’s very thorough and well organized.

    Coincidentally, I was just having a discussion about this very topic with a customer yesterday. It’s always surprising to me what kinds of factors influence decisions like these. Popularity of a particular tech stack vs. simplicity and user experience are big ones. But, things like confusion around package size limits or potential edge case scaling issues once “we get tons of traffic” are the kind of thinking that very often lead us down a weird road.

    Hopefully this guide will help customers make sound decisions at the right moments in their dev cycles.

  10. Decision Guide: AWS Fargate or AWS Lambda?

    AWS Fargate or AWS Lambda?

    https://docs.aws.amazon.com/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.html

    There is a new and very useful decision making guide for those wondering if AWS Fargate or AWS Lambda is the right kind of compute. It’s very thorough and well organized.

    Coincidentally, I was just having a discussion about this very topic with a customer yesterday. It’s always surprising to me what kinds of factors influence decisions like these. Popularity of a particular tech stack vs. simplicity and user experience are big ones. But, things like confusion around package size limits or potential edge case scaling issues once “we get tons of traffic” are the kind of thinking that very often lead us down a weird road.

    Hopefully this guide will help customers make sound decisions at the right moments in their dev cycles.

  11. Decision Guide: AWS Fargate or AWS Lambda?

    AWS Fargate or AWS Lambda?

    https://docs.aws.amazon.com/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.html

    There is a new and very useful decision making guide for those wondering if AWS Fargate or AWS Lambda is the right kind of compute. It’s very thorough and well organized.

    Coincidentally, I was just having a discussion about this very topic with a customer yesterday. It’s always surprising to me what kinds of factors influence decisions like these. Popularity of a particular tech stack vs. simplicity and user experience are big ones. But, things like confusion around package size limits or potential edge case scaling issues once “we get tons of traffic” are the kind of thinking that very often lead us down a weird road.

    Hopefully this guide will help customers make sound decisions at the right moments in their dev cycles.

  12. Stolen from threads.

    Kid: Mom can we have Farscape
    Mom: We have Farscape at home.
    The Farscape at home:

    #stargate #farscape #fargate

    please note there isn't an Alt Text because my brain is refusing to allow me to describe it succinctly

  13. Stolen from threads.

    Kid: Mom can we have Farscape
    Mom: We have Farscape at home.
    The Farscape at home:

    #stargate #farscape #fargate

    please note there isn't an Alt Text because my brain is refusing to allow me to describe it succinctly

  14. Stolen from threads.

    Kid: Mom can we have Farscape
    Mom: We have Farscape at home.
    The Farscape at home:

    #stargate #farscape #fargate

    please note there isn't an Alt Text because my brain is refusing to allow me to describe it succinctly