Explore the Platform: slavecode.codes
Support on GitHub: github.com/phero20/slavecode (Give it a star)
Recently, I woke up to an unexpected GitHub notification. Herman Zvonimir Došilović, the creator of Judge0, opened an issue on the SlaveCode repository to say he enjoyed the project.
Even better, he added the SlaveCode repository to the official Judge0 README.md showcase.
Judge0 is one of the most widely used open-source code execution engines available, and it serves as a critical component in SlaveCode's architecture. Having the project recognized by its creator is a great milestone. I wanted to share a brief overview of why we chose Judge0 and how it fits into our system design.
Why Judge0?
When building SlaveCode, a platform that compiles and executes user-submitted code in real-time, security and isolation were the highest priorities. Running arbitrary code safely requires a robust sandbox environment.
As detailed in my Full Architecture Walkthrough, SlaveCode relies on a strict multi-cloud topology. While the primary REST API and databases are hosted on Google Cloud Platform (GCP), the code execution engine is completely isolated on Microsoft Azure VMs.
Judge0 was the perfect fit for this isolated environment. By leveraging its heavily containerized execution environment on Azure, we ensure that the execution sandbox is physically separated from our core databases and API infrastructure. This separation of concerns means that the blast radius of any potential sandbox escape is strictly contained, keeping the main platform and user data completely secure.
By offloading the complexities of secure compilation and execution to Judge0, the SlaveCode backend is free to focus entirely on its core platform logic and features.
The Value of Building in Public
This recognition reinforces an important lesson: documenting your engineering decisions is just as important as the code itself.
Herman likely discovered SlaveCode because I took the time to write a detailed architectural breakdown of the platform on Dev.to. Sharing the reasoning behind our technology stack, the trade-offs we accepted, and the problems we solved helped the project reach the right people in the open-source community.
If you are building a platform that requires secure, scalable code execution, I highly recommend checking out Judge0 and giving the repository a star.
Thank you to Herman and the open-source community for providing the tools that make projects like SlaveCode possible.
(If you like the project, I would love a star on the SlaveCode GitHub repository!)