System Design :

• we have an API server (Node JS) → which will handle our requests RESTFULLY (from RESTFULL APis)

REST → Representational State Transfer , where we’ll basically transfer back the state to the clients i,e. server won’t store the state (request’s info) of the client and while giving back we will represent them(clients) the results that we have fetched from the server. All of those APis’ which follow this → RESTFULL APis

FUNTIME

https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQoAMkFNgF4pPRp3aR0enZe4jK4YYBkRS0WnRg99iQmJy6CQ58Q4ILix13w1Vz5G06R7Pc&usqp=CAU

• Now , user will post a request towards our server as → take my this git’s URL and deploy it
• we now have src code in gitHub , now we instead of cloning the code onto server , bcz code wud be too large , also wud be hard to build it b4 deploying so we’ll use 🐳-DOCKER -an isolated env , with AWS ECS - Elastic Compute Service.
• we’ll give the url of git to take the src code from , and behalf of client the docker engine will clone the code onto its ISOLATED ENVIRONMENT , ADVTANGES OF THIS METHOD → 1. we’ll save the storage space of the API SERVER , 2. And also i can attain PARALLESIM (TASK LEVEL (diff data diff tasks) , DATA LEVEL(same task is been executed by diff subtasks of a task and running them) ) in the context of docker like → running application in container and DB on other one , is task parallelism and splitting the DB into smaller chunks and process each one in a separate container.
• By Now, our clients’ codes have been built/cloned successfully into the isolated ENV (containers) and now after this we should be passing the output folders or .exes which been produced for us after been built in docker be passing this onto the Central Data Storages → like inn here we are using 🪣S3 Data Buckets , by AWS.
• Aight!! , BROther but how to retrieve them in a safely , securely , efficiently O_o ? → we’ll be having codes(executable forms) of each user inn S3 by now , to retrieve we’ll be using ‘CUSTOM REVERSE PROXY’

below here is the traditional way of → ‘how browsing on the internet works usually’

below is our method of → ‘How a reverse proxy server works’

Forward Proxy : is a server that acts as an intermediary between a user's device and the internet and can Hide web server IP address , Protect the Users , Mask their Identity mainly for : boost security for users in a private network, mask the original IP address to ensure anonymity and control and regulate traffic that passes back to the end user

Reverse Proxy : a server, app, or cloud service that sits between web servers and client requests, forwarding the requests to the servers and then returning the server's response to the client.

It’s so called ‘FUNTIME’ Again :))