As an AWS focused solutions/systems architect, I’ve been feeling this for the last 10ish months too. I attended the first 9 re:Invent conferences (up until Covid upended things) but I was glad I didn’t attend last year; and re:Inforce sounds like it was even worse.

  • fubarx@lemmy.ml
    link
    fedilink
    arrow-up
    16
    ·
    4 months ago

    AWS bread and butter is EC2, S3, and Lambda.

    The reason AWS is focusing so much on Gen-AI is because they’re in the shovel-and-pick business during the gold rush. This guy’s beef should be with the over-excited gold speculators, not the general store purveyors of denim and panning equipment.

    • 👍Maximum Derek👍OP
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      4 months ago

      But in the mean time EC2 hasn’t gotten a meaningful feature that’s not to accelerate training or inference since GP3, and people folks are backing away from serverless-first designs because cost-control and other features we’ve been screaming for for several years aren’t being addressed.

      Edit to add: on the EC2 side I forgot we got Gravaton3 processors like 18 months ago. That was appreciated for sure.

      • 1984@lemmy.today
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        4 months ago

        Aws serverless is a scam also. Lambda with step functions just to run some functions in order without having to scale servers?

        Its just ridiculous how much complexity it adds, and the performance is abysmal compared to local function calls as well. It’s like younger devs have never written a fast application without aws.

        • i_am_not_a_robot
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 months ago

          In theory, running a serverless function can provide adequate response times at costs that are unreachable with private servers. It’s basically those services that would run your application for few minutes every time it received a request, but with theoretically lower overhead since it’s supposed to be a function instead of a full application.