Should I Use Fargate, Lambda, or EC2 to host my application?

Поделиться
HTML-код
  • Опубликовано: 21 янв 2021
  • Get the DevOps Roadmap for 2022 here: devopsfordevelopers.io/roadmap
    Which AWS service is the right choice for you and your team when it comes time to host your application in AWS? In this video, I cover 3 options from AWS: Fargate, Lambda, and EC2.
    **************************
    Links mentioned in video:
    Which cloud provider should you use: • Heroku Or AWS? Which c...
    Dealing with Vendor Lock-in and cloud providers: • It happened to Parler,...

Комментарии • 34

  • @DevOpsForDevelopers
    @DevOpsForDevelopers  2 года назад +1

    The DevOps Roadmap for 2022 is available for free at devopsfordevelopers.io/roadmap
    One of the hardest things about learning is understanding how the different components work together. Using this guide, you start with a topic that interests or relates to you. At the end of the section, other related topics are shown allowing you to pick and choose your own path to DevOps mastery.

  • @kaypakaipa8559
    @kaypakaipa8559 Год назад +2

    Great video bro, concise, Fargate sounds like what I'm looking for

  • @nahuelalberti5963
    @nahuelalberti5963 Год назад +5

    4:20 Thats why you should use terraform or CDK modules to replicate architectures! Manual settings could be a good start for somebody thats not familiar with the service to use, but once you get it, its better if you dont have that manual task, as you say, maybe somebody in your team needs to do the same and make a mistake, or maybe you are in a bad day and make some mistake!. Nice video!!

  • @dvsrinath
    @dvsrinath 3 года назад +1

    Excellent presentation and explanation, thanks.

  • @rickharold7884
    @rickharold7884 2 года назад +2

    Cool. Thx

  • @vandark1233
    @vandark1233 Год назад

    thanks for share your knowledge very useful

  • @carol00210
    @carol00210 5 месяцев назад

    If you would remake this video today, would you change your opinion that lambda functions are maybe not ready for mainstream yet?

  • @lashlarue7924
    @lashlarue7924 10 месяцев назад +1

    Word up, my homeslice. 🤙

  • @jaafarzagdoud6103
    @jaafarzagdoud6103 2 года назад +1

    Hey hello great video! I have a question, is it possible to build with lambdas a marketplace that you wanna scale and get big in the future?

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад +1

      Sure, it's definitely possible. You'll need to architect your application with that in mind though.

    • @jaafarzagdoud6103
      @jaafarzagdoud6103 2 года назад

      @@DevOpsForDevelopers would you mind to explain to me what's the best thing to do? And are you available for a talk? Maybe we can work together.

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад

      @@jaafarzagdoud6103 devopsfordevelopers.io/discord

  • @arunkumar-us8ei
    @arunkumar-us8ei 3 года назад

    Is it possible to build a microservice architecture with lambda?

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  3 года назад +2

      Hey Arun,
      It sure it. Using lambda functions as the core of your microservice and SQS queues to decouple the microservices from each other is a solid plan.
      A couple of considerations to note: if your microservices don't have a lot of activity, the cold boot/warm up time for first response may impact performance. You'll also want to understand how heavily your lambda functions will be used to ensure to are provisioned correctly for concurrent executions. This will help prevent incoming requests from hanging due to no lambda executors available to service the request.

  • @kristhudas726
    @kristhudas726 2 года назад +1

    is it easy to migrate a AWS lamda based gradle project to host on fargate ?

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад

      At a conceptual level, yeah. Build your project to run as a docker container and launch it there.
      The other considerations are:
      - why move it to Fargate?
      - do you have Fargate already setup or is this a new environment?
      - what other dependencies will be impacted (databases, caches, etc...)
      After addressing those questions, if Fargate still seems like the right choice, a good first step would be to build and run your application locally in a docker container using Docker Desktop.

    • @kristhudas726
      @kristhudas726 2 года назад

      @@DevOpsForDevelopers
      Thanks for addressing my comment
      I am still confused because
      At the moment my lambda function takes input line(from input CSV) and for every input line it performs some operations and generates output CSV files and stores it in S3 bucket
      As we all know we have time and memory restrictions with AWS
      lamda(i.e, 15 mins)
      We had to create multiple lamda functions to generate csv's for all our input lines
      As it is becoming complex day by day as the input lines are increasing
      We are looking for an alternative solution?
      Can you please suggest which service we should go for ?
      And yeah we are completely new to aws fargate

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад +1

      I gotcha. Yeah, Fargate would work for that but since you're describing an ETL job, I'd check out AWS Data Pipeline or AWS Glue (though Glue uses Lambda under the hood so I'm not sure you'd gain much by pursuing it)

  • @keplerk
    @keplerk 2 года назад +2

    From my little experience with lambdas, they are very useful when you have to develop some basic to medium complexity rest apis, due them working on demand, it's a huge budget save because they don't work 24/7 but only whenever they are called.

  • @jimknoll
    @jimknoll 2 года назад +1

    Edit your lambda live from console goes away for large code. And use cloud formation or tf and you will see the change some one made via console. All config is code You just need to buy in. Just as good between lambda when you treat confit as code

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад

      Good points!

    • @cremedelacremeoflego
      @cremedelacremeoflego 2 года назад +1

      @@DevOpsForDevelopers I think you can also use the "lambda:UpdateFunctionCode" IAM permission to deny developer user accounts from actually changing lambda any lambda code. Then just assume a deployment role in CI that has the higher level of access needed to update the lambda code?

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  2 года назад

      @@cremedelacremeoflego nice!

  • @prerakhere
    @prerakhere Год назад +1

    I thought most people go with ECS with EC2 instead of ECS with Fargate for their web servers due to former being less expensive.

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  Год назад

      This is my experience only, I don't have data to know which is more popular overall.

  • @abdirahmann
    @abdirahmann Год назад +1

    how cheap is fargate?

    • @DevOpsForDevelopers
      @DevOpsForDevelopers  Год назад +1

      It's priced based on utilization. calculator.aws/#/addService/Fargate