Design LeetCode - System Design Interview

[@michaelpio8258]

The quality of your content is Great , keep the good work up!

[@Hufsa]

this is so well detailed, I didn't expect so great material in less than 20 minutes, impressing

[@SystemDesignSchool]

Thanks, glad you liked it!

[@amithgangarapu]

The video and your explanation is just perfect! I hope your channel grows.

[@inventorokoth]

keep going man. really helpful what you're doing

[@Bhaavgeete-ij2zs]

Wow.......Simply amazing. The quality of content surely deserves a Million Followers. Keep going this way, eager to learn more from you.

[@elitegamer8008]

Ohh nice video all the best for future Endeavours and bring more system design videos like this

[@SystemDesignSchool]

Yes, we will! Thank you for being our first comment!

[@shivanshbhat1056]

This is really helpful. Thanks !

[@arshdeepkumar]

using docker will still leak your code, message queue and db keys that you still will need to subscribe to queue and save results to DB maybe a way to disable file access and network for user programs

[@SystemDesignSchool]

user code runs in docker container has separate filesystem namespace and cannot access other processes

[@arshdeepkumar]

I mean in the docket container you'll have source code ? For polling and executing code ?

[@yosifsalim-nz3mp]

what did you use for documenting the API ?

[@SystemDesignSchool]

I used the tool here to document it and have AI grade it: systemdesignschool.io/problems/leetcode

[@XxRazcxX]

On 4:37 u said 556 Read QPS and 5.56 write QPS. Then on 5:47 you say 556 Write QPS and 5.56 Read QPS.

[@XxRazcxX]

I personally think its 556 WRITE QPS since submission are saved.

[@SystemDesignSchool]

Oh oops, it should be read 556 since the assumption is read:write 100:1 (we requests info from the server a lot more than we submit solutions)