this post was submitted on 23 Jul 2024
21 points (100.0% liked)
Technology
37696 readers
256 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
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.