[jjevanoorschot]

The title is editorialised to be clickbait. The original title is "Scaling up the Prime Video audio/video monitoring service and reducing costs by 90%".

They changed a single service, the Prime Video audio/video monitoring service, from a few Lambda and Step Function components into a 'monolith'. This monolith is still one of presumably many services within Prime Video.

[kstenerud]

The subtitle is "The move from a distributed microservices architecture to a monolith application helped achieve higher scale, resilience, and reduce costs."

And the article itself mentions the 90% cost reduction.

So the title seems pretty much in-line with the original intent.

[jjevanoorschot]

The title makes it sound like Prime Video abandoned microservices all-together, but in reality they only did so for a single service.

[herculity275]

Prime Video has hundreds of teams, VQA is a tiny team that owns a very specific QA service. Omitting that distinction from the title absolutely is clickbait.

[oaiey]

The worth here is that Amazon is writing about not going into AWS PaaS native programming (what Lambda is) because it is too expensive for them.

That has some newsworthiness and the title kind of reflects that.

[dragonwriter]

> The worth here is that Amazon is writing about not going into AWS PaaS native programming (what Lambda is) because it is too expensive for them.

…and going to a newer AWS service (ECS), instead.

[oaiey]

IMHO, ECS is more closer to IaaS than PaaS. And therefore the lock-in is much less bad than with the serverless PaaS approach

[hobofan]

> newer

~9 months almost a decade ago, so not substantially newer.