Prime Video service dumps microservices, cuts AWS bill 90%
thestack.technology
Prime Video service dumps microservices, cuts AWS bill 90%
1–10 of 42 posts
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#2Article's headline and text mention this was achieved by switching from Lambda to ECS, which makes a lot of sense. Lambda is expensive for frequently used services.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#3Here’s a link to the actual blog post from Amazon: https://www.primevideotech.com/video-streaming/scaling-up-th...
It’s worth noting that the team that wrote the article is just a small part of Prime Video. The headline can definitely be interpreted to mean the entire Prime Video service.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#4Previous thread -- https://news.ycombinator.com/item?id=35811741
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#5Don't buy retail, buy wholesale, unless you are buying a small amount.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#6This sounds like a bad first design:
- didn’t just grab the whole video (or ~1min segment), but individual frames
- put each detector in its own context, needing its own copy
- created a StepFunction for each tiny piece
This never would’ve passed design review when I worked at Amazon because the combinatorial blowout is obvious and predictable.
I’m sure they switched to what was considered good practice even then:
- a single StepFunction per video
- a batch step across segments
- downloading in bulk, to a single container
- running all the detectors together
The problem wasn’t serverless or micro services: this was just bad design.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#7Monoliths have local CPU L1-Cache speeds, distributed microservices have JSON desearlization,searlization, network round trips.
Distributed stateless monoliths can be faster than microservice.
Carbon foot print, cloud bill of too many microservices is probably high.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#8This sounds like a bad first design: - didn’t just grab the whole video (or ~1min segment), but individual frames - put each detector in its own context, needing its own copy - created a StepFunction for each tiny piece This never would’ve passed design review when I worked at Amazon because the combinatorial blowout is obvious and predictable. I’m sure they switched to what was considered good practice even then: -…
If this was a system design interview, would this design be approved?
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#9This sounds like a bad first design: - didn’t just grab the whole video (or ~1min segment), but individual frames - put each detector in its own context, needing its own copy - created a StepFunction for each tiny piece This never would’ve passed design review when I worked at Amazon because the combinatorial blowout is obvious and predictable. I’m sure they switched to what was considered good practice even then: -…
This assumes the current functionality is the same as it was when it was originally created.
Re: Prime Video service dumps microservices, cuts AWS bill 90%
#10This sounds like a bad first design: - didn’t just grab the whole video (or ~1min segment), but individual frames - put each detector in its own context, needing its own copy - created a StepFunction for each tiny piece This never would’ve passed design review when I worked at Amazon because the combinatorial blowout is obvious and predictable. I’m sure they switched to what was considered good practice even then: -…
This assumes the current functionality is the same as it was when it was originally created.
The article from Prime Video says that it has largely the same functionality, while outlining problems from the initial version.