[dead]
Scaling up the Prime Video audio/video monitoring service and reducing costs
191–200 of 526 posts
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#192I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.
I had to google what 'cargo culting' meant. But I laughed when I found out.
https://en.wikipedia.org/wiki/Cargo_cult_programming#:~:text....
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#193Next they will transition to on premises hardware from the cloud to save another 90%.... oh wait...
I wouldn't be surprised if AWS started a on-prem hardware leasing service. Some company are providing "On-premise As A Servicse" solution.
They already do ^_^. AWS Outpost[1]
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#194My word. I'm sort of gob smacked this article exists. I know there are nuances in the article, but my first impression was it's saying "we went back to basics and stopped using needless expensive AWS stuff that caused us to completely over architect our application and the results were much better". Which is good lesson, and a good story, but there's a kind of irony it's come from an internal Amazon team. As another…
There was an article not long ago from AWS saying they'll be focussing on cutting cost for customers. Maybe the next step of that process will be pushing their clients off of AWS and telling them to just host on prem.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#195I'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 works better if you don't trust other team. While having trust seem like a basic thing, this is absolutely not the case for a lot of companies. With microservices, it is easy to see services which are down or have high error rate or latency, have clear API contract and call out the team for breaking API contract, and assign cost for which the teams have incentive to reduce, or at least not increase it.
I haven't worked on a microservice architecture yet, but this is a very interesting idea that I hadn't heard before. That micro services can potentially give greater visibility of each team's performance, improving accountability.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#196I'm pretty convinced that microservices are one of those things that make sense 5% of the time and the other 95% is cargo culting.
Yeah, but writing a big chunk of new code always involves either gambling or cargo culting, until you nail the actual requirements and the design. MSA is just a methodology to contain risks from the uncertainty, and it never says you must build everything in MSA. It's often better to migrate mature code into (semi-)monolithic services.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#197At this point isn't the lesson to use serverless stack for fast iterative processes then use a custom solution once you know exactly what you want?
I have 0 experience with serverless/cloud. Just a thought.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#198Earlier quoted context omitted.
Another pain with monoliths is that they can only be deployed if the entire monolith is passing all tests. When you cannot deploy your changes because someone else on an entirely orthogonal team broke something in the monolith which is not related to you it gets old really quick. Large monolithic repos with many independent targets for testing and deployment work the best at huge scales. If you are only a few hundred…
Tests passing should be a gate to merge into main. Tests can also be run in parallel.
Two green changes merged to a green main can produce a red main.
This is not a commonly known fact. Just to take an example of GitHub, this check is disabled by default:
> Require branches to be up to date before merging
> Whether pull requests targeting a matching branch must be tested with the latest code.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#199This really is a click bait title. They are talking about their video quality monitoring service, not their video streaming service. It’s something they use to check for defects in the video stream - hence the storing of individual frames in S3. Original title: Scaling up the Prime Video audio/video monitoring service and reducing costs by 90%
Yes this is a ridiculous clickbait. For once the original title is not and the poster had to make it so... Why is dang not changing it back?
PrimeVideo is very much based on a microservice architecture. Hell, my team which isn't client facing and has a very dedicated purpose has easily more microservices than engineers.
Re: Scaling up the Prime Video audio/video monitoring service and reducing costs
#200My word. I'm sort of gob smacked this article exists. I know there are nuances in the article, but my first impression was it's saying "we went back to basics and stopped using needless expensive AWS stuff that caused us to completely over architect our application and the results were much better". Which is good lesson, and a good story, but there's a kind of irony it's come from an internal Amazon team. As another…
But they migrated to AWS ECS that still is an expensive serverless AWS stuff, just fully managed by Amazon.