Design a Code Execution System | System Design

Table of Contents:
0:00 - Introduction
0:38 - Requirements
1:35 - Single Server
2:43 - Docker
4:00 - Kubernetes
5:19 - Kubernetes Standby Pod
6:43 - Conclusion

Socials:

[randomforest_dev]

I am confused. The explanation is not specific to 'Code Execution System' logic, it is just distributed scaling in general.

[harisridhar]

I really like your presentation style and explanation style ; you do a fantastic job incorporating multi-colored visual elements, and personally, it helps me to digest and focus on the multiple running pieces of the architecture : basically viewer engagement.

[rigveddesai]

i am not sure why we can't just run a basic check on the server side when it spins up for whether the standby container exists or not? why is this not optimal? is the server initially checking for the container, accordingly spinning up/using existing standby and then assuming the standby container exists for the entirety of its uptime a bad idea?

[Rustamushko]

I expected to see an architecture of scalable FaaS with interpreters\compilers. K8S is a concrete orchestration system which shall be selected among other similar systems based on some rationale. How a user receivers execution result? Synchronously or asynchronously - nothing about this?

[mateuszsiwiecki]

Hi, I really like your channel and have learned a lot from it. However, in this particular case, I think your solution is not good enough because it mixes application with infrastructure. In this case, a Docker in Docker solution would work much better. With such a solution, you would separate the process of load balancing and providing access to your service from the application itself, for which it would be necessary to create an environment for the given language on an ongoing basis.
Besides that, keep up the good work. I always look forward to your next videos!

[bhanuprakashrao]

Containers are run on an linux nodes using c-groups.