Back to Monolithic App? | Prime Video Case Study | Microservices to Monolith | Tech Primers

preview_player
Показать описание
This video covers Amazon Prime Video's move towards Monolithic architecture from Serverless/Microservices based architecture to save cost and scale faster than before.

📌 Chapter Timestamps
=====================
00:00 - Intro
00:33 - Agenda
01:03 - Prime Video Audio/Video Monitoring Service
02:31 - Initial Serverless Architecture
06:08 - New Monilithic Architecture
08:15 - Scaling the Monolith
09:31 - Results and Takeaways

Join this channel by contributing to the community:

📌 Related Links
=============

📌 Related Playlist
================

🎬 Video Editing: FCP

---------------------------------------------------------------
🔥 Disclaimer/Policy:
The content/views/opinions posted here are solely mine and the code samples created by me are open sourced.
You are free to use the code samples in Github after forking and you can modify it for your own use.
All the videos posted here are copyrighted. You cannot re-distribute videos on this channel in other channels or platforms.
#SystemDesign #SystemDesign #TechPrimers
Рекомендации по теме
Комментарии
Автор

11:33 Yes, totally agree. Think first instead of moving into the new fashion tech stack.

pguti
Автор

Great summarization of the Prime Video Case Study!

Shiladitya
Автор

When I was in computer science school twenty years ago, we were taught that "silos are bad" which microservices are based upon silos. I think the pragmatic real world answer is "it depends" as Amazon is learning in this case study. Monolithic and microservices are both tools in our toolbox.

mefirst
Автор

One of the main advantages of microservices is that multiple teams can focus solely on their service, making the release/deployment cycle faster, along with benefits such as independent scalability. With a monolith, cross-team dependencies will increase, and the release/deployment cycle will slow down adding scalbiltiy challenges.

So, it seems like there is a trade-off between cost savings and quick deployment/maintenance.

mavurugangadhar
Автор

Agreed I'm not sure this is monolithic in nature. Also microservices have to be evaluated to see if they are the best tool to use. There is a lot of variation in what comprises a microservices and often discussion of a nanoservice vs a microservices. Microservices are often broken by domain and hence can have more then one piece of functionality grouped in the service. When choosing architecture it always comes down to it depends and of the largest factors is cost.

spmurray
Автор

Nicely explained. Important point is that people making a buzz that entire Amazon Prime is moving away from Micro-Service architecture is wrong, its just their monitoring system, the old architecture seems over engineered to use S3, Lambda, Step functions for such high volume real-time video stream analysis and defect detection system, with the new architecture they just doing in single process to reduce the data transfer and persistence cost with improved performance as data transfer and processing happens now in-memory.

niranjankk
Автор

From the study it is clear that this has been implemented for one functionality of error detection and smoother rendering of videos, not the total application but a contained function. So the earlier decompetition was mainly over engineering... Is my summarised understanding correct?

gautamsinha
Автор

Thank you for the detailed information 🙂

JaNaMSoNi
Автор

Thanks for this excellent explanation but is this really a monolith? This service has a very specific task and also stateless which would give a significant cost saving

Jokikiolu
Автор

LOL 😂 previously the craze was for Serverless now its going back again 😂

ru
Автор

Bro Monolithic it's like a rod currently I am working on the Monolithic project for small change we are doing re deployment and it will takes forever....8 hrs this bothers me with this issue we are thinking 10 times is this change is required or not...to fulfill that functionality in other ways but our hairs are falling down but no way we will found eventually or finally We need to change the code 😊

itsnarahari
Автор

too many microservices are really a mess.... 😭 sometimes i think to give up my software engg job.

crimsonx_
Автор

Is the final video which is uploaded to S3 saved permanently or is it recomputed for every client request for the same video? Or is it region-wise S3 videos are separated and reused?

prvinsharma
Автор

Will Amazon prime cost reduce from this

garavind
Автор

But I think they are still using replication for the s3 🪣. Each s3 prefix link only support 5k read head and 3k write head .The only outbound rule is from s3 to cdn .I think they did use S3 replication and reading the data to CDN and return to the users with closest Starbucks locations and it still need eventdriven microservices .Overall it didn’t fully migrate to the monolith way.

phyohtetpaing