A Cloud Based IDE

So Now that you have learnt the basics of Docker, we’ll now hopp onto using it in some of the projects.

As the name says its Repl.it Clone, not much focussed on the frontend and UX, but mainly focused on backend and the data paths been taken, and the Docker working.

By this we provide the user:

• A In-Browser Terminal ($bash)
• A file system hierarchy for user’s files
• A Server which is Dockerized and runs on submission

This ‘Dockerized server’ may run on top of any of the Cloud Providers like AWS, GCP, can even be Clusters of Kubernetes……. but, we’re gonna use AWS (ECS)

So the basics idea is to simulate whatever the actions like writing, updating, running the codes done by the user inside a docker, by providing an isolated environment for the user, thus execute them for the user and get back the website with the data.

As soon as the user creates a playground | | Then we request the server behalf of the user to create a playground for him | | then the server will now spin-up a new docker container for the each user | | and the public IP of this docker container, will now return the terminal to the user, so that the browser’s terminal will now have a connection with the server inside of the container

https://app.eraser.io/workspace/zx3vc6rl6efr0G9dtFYQ

Ok but is the system Architecture we’ve followed highly scalable?

Yes, it is because we’ve popped up a new container for every new user out there.