Live data from Hacker News

Scaling up the Prime Video audio/video monitoring service and reducing costs

primevideotech.com

11–20 of 526 posts

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#11
post #6

Sending video frames between services is expensive, also doing per state transition hosting on things doing state transitions multiple times per second in a single stream is also expensive... Like, did they even think about cost when designing this the first time?

why should they, they're richer than God!

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#13
post #6

Sending video frames between services is expensive, also doing per state transition hosting on things doing state transitions multiple times per second in a single stream is also expensive... Like, did they even think about cost when designing this the first time?

Considering they don't actually pay the bill for this and it is internal accounting, probably not. Belt tightening has probably pushed cloud providers to figure out if they're wasting stuff they could put to better use, and I assume when it launched and nobody was watching Prime Video, inefficiencies were both smaller and less noticeable.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#14
post #10

I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.

As for me,I have been trying to discover that 5% that cannot be done without microservices.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#15
post #10

I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.

microservices make a lot of sense organizationally where each feature team can own their own feature service.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#16
post #8

I'd be surprised if this doesn't get taken down as it casts AWS lambda in an unfavorable light (and rightly so). That's the impression I have of Amazon's leadership but maybe I'm wrong.

> We designed our initial solution as a distributed system using serverless components (for example, AWS Step Functions or AWS Lambda), which was a good choice for building the service quickly.

The message seems more that they outgrew AWS lambda but that lambda was a good choice at first.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#18
amazon product ditches amazon product for another amazon product?

feels very strongly they just moved from one AWS platform to another.

delay between asynchronous communicating processes differs in these architectures and I suspect they were unable to orchestrate microservices to match the RPC "inside" a monolith model. Nobody can: It only matters if your IPC is causing delay you can avoid.

Most of us aren't in a room where the real cost is high: 90% of computers are more than 90% idle 90% of the time. Amazon is not in that cohort.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#19
post #10

I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.

microservices make a lot of sense organizationally where each feature team can own their own feature service.

I would argue that in such cases those are not "micro" services anymore, they are services. In that case it makes sense to develop and deploy them separately, then find a way to make them talk to each other. Microservices is a different architectural decision.

Re: Scaling up the Prime Video audio/video monitoring service and reducing costs

#20
post #10

I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.

microservices make a lot of sense organizationally where each feature team can own their own feature service.

OR each team can write their features as a python package, rust crate, go module to be included in the main app. Libraries, versioned.
Post reply on HN