Тёмный

System Design Framework (For Interviews and beyond) 

The Geek Narrator
Подписаться 71 тыс.
Просмотров 4,5 тыс.
50% 1

Опубликовано:

 

29 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 11   
@thegaminggum
@thegaminggum Год назад
Really interesting, dont want to disrupt the perfect 69 likes figure instead subscribing to the channel.
@TheGeekNarrator
@TheGeekNarrator Год назад
Thank you 😀🙏🏻
@amanrai8010
@amanrai8010 2 года назад
We are down with 4 bears and watching this video .
@TheGeekNarrator
@TheGeekNarrator 2 года назад
Hahaha enjoy
@amanrai8010
@amanrai8010 2 года назад
Capacity estimation part was pretty great i would suggest make a separate chapter from this video for that.
@sandeepbhat676
@sandeepbhat676 2 года назад
thanks for such type of content, please keep going
@TheGeekNarrator
@TheGeekNarrator 2 года назад
Thank you Sandeep for the feedback. Please keep supporting 🙏🏻😊
@RAJATTHEPAGAL
@RAJATTHEPAGAL 2 года назад
SQL is highly unpopular, might just agree 😵😵 le me : Writing 3NF forms for every entity and assuming interviewier is fine with me using SQL Databases only to be asked why not slap Cassandra on this and call it a day. 🤦‍♂ Happened a while back. Was waiting on this podcast. API versioning is something I will definitely be taking away. I myself have never talked about that or though of it to be addressed in an interview. 😃
@TheGeekNarrator
@TheGeekNarrator 2 года назад
Thanks Rajat for watching the video and sharing your experience. Yeah - API versioning is critical and there are multiple ways for doing that. I suggest taking a look at API Design Masterclass where we talk about different ways of versioning an API.
@vishwaspatel4276
@vishwaspatel4276 2 года назад
Great video, got amazing insights. One thing I wanted to dig deeper is choosing compute in capacity planning. Are there some standard methods to determine if my system with "x" cores and "y" GB RAM is good enough to serve my application to "n" number of users. Load testing is the first thing which comes to my mind, just curious to know how such decision are taken in general.
@TheGeekNarrator
@TheGeekNarrator 2 года назад
Hi Vishwas, Thanks for watching the video and showing your interest. Specifically for your question, I would say typically we figure out what type of workload it is i.e. IO, Memory or CPU intensive. Once we know that we try to make some calculations based on the req/s for IO, data size for memory and algorithm complexity for CPU intensive tasks. Then best is to test the workload on a single machine and figure out the breaking point. Once you know the breaking point it is typically easily to figure out bottlenecks and also find the scaling model for your application. Hope it helps, Good luck 🙏🏻😊
Далее
КОТЯТА В ОПАСНОСТИ?#cat
00:36
Просмотров 1,2 млн
ДЕНЬ УЧИТЕЛЯ В ШКОЛЕ
01:00
Просмотров 1,4 млн
System Design Interview: Design Amazon Prime Video
26:53
Distributed SQLite with Litestream and LiteFS
54:37
Просмотров 10 тыс.
DHH discusses SQLite (and Stoicism)
54:00
Просмотров 76 тыс.
AWS DynamoDB (Internals) Masterclass with Alex Debrie
1:31:48