Forward Proxy and Reverse Proxy | System Design Interview Basics

[@jadeedstoresupport8916]

I have seen many videos on Forward and Reverse Proxies; to me, this video has been the most clarifying. If the video presenter puts in great effort in making the video, then a short video could be a lot more potent and insightful. Many thanks

[@marcosbarrera8183]

Thanks for your video.
Simple, directly to the grain. Wonderful!

[@ByteMonk]

Thank you 😊, you may like to check out the playlist of short videos like these, link in description

[@um4r_arf]

wow explained simply, thanks man

[@bensassiprogramming]

thank you so much brother you explain really well !!
please with what tool you are doing the animation is amazing

[@ByteMonk]

Thank you! FCP or Adobe Products

[@mithunrahman8978]

great

[@yrusTube]

Hi, nice and simple illustrations. May I ask what did you use?

[@ByteMonk]

Thank you, I use apple and adobe softwares, such as fcp, premiere pro, animation

[@yrusTube]

Thanks, follow up question.
Is it easier to create animations of the circles and arrows you do in premier pro vs PowerPoint?
I am creating mine in PowerPoint, only because I have years and years of experience using it. And recording it and putting it in iMovie and voice using AI.

[@ByteMonk]

@@yrusTube Sorry, I can't compare the tools as I am not well versed with Power point, regardless, animation takes a lot of time.

[@govardhanreddy690]

Thank you 💞

[@yrusTube]

Also may I ask how many hours does it take you to make one video?

[@ByteMonk]

Anywhere from 10 - 20 hours for a 5-10 mins video end to end

[@yrusTube]

@@ByteMonk thanks for reply. I have been working on my first video it’s been like forever more than 20 hours already 😄

[@ahamedkaize1634]

If the reverse proxy server is not on the same network as the destination server, can we configure the destination server's external URL or IP address?

[@ByteMonk]

Yes, if the reverse proxy server is not on the same network as the destination server, you can configure the destination server's external URL or IP address.
When a reverse proxy server is used, the client requests for a resource from the proxy server, and the proxy server forwards that request to the destination server on behalf of the client. The destination server then responds back to the proxy server, which in turn sends the response back to the client.
In this scenario, the client is not aware of the destination server's actual IP address or URL because it is communicating only with the proxy server. Therefore, it is the responsibility of the reverse proxy server to forward the request to the correct destination server, even if it is located on a different network.
To achieve this, you can configure the reverse proxy server with the external URL or IP address of the destination server. This will allow the proxy server to correctly route requests to the destination server, regardless of its location.
It is important to note that when configuring the external URL or IP address of the destination server, security considerations should be taken into account. It is recommended to use secure communication protocols such as HTTPS, and to implement appropriate security measures such as authentication and access control to prevent unauthorized access to the destination server.

[@ByteMonk]

Let's say you have a reverse proxy server located in a public cloud, and a web server located in a private data center behind a firewall. You want to configure the reverse proxy server to forward requests to the web server.
The web server has an internal IP address of 192.168.1.10, and its internal URL is webserver.internal. However, since the web server is not accessible from the public internet, you need to configure the reverse proxy server to use an external IP address or URL to forward requests to the web server.
Assuming you have a public IP address for the reverse proxy server, you could configure the proxy server to forward requests to the web server using its external IP address. For example, you could configure the proxy server to forward requests for proxyexample.com to 192.168.1.10.

[@ByteMonk]

Here is an example in Nginx
server {
listen 80;
server_name proxyexample.com;
location / {
proxy_pass 192.168.1.10;
}
}

[@ahamedkaize1634]

@@ByteMonk Thanks for your super fast and informative reply.
My use case is : The destination server requires all the traffics to come from fixed public address which will be whiletelisted in the destination server. But the Users are connecting to the internet via home router so there is no fixed public IP address, which is the reason we are planning to route all the traffic via a proxy server that will have a fixed public IP and it will be whiletelisted at the destination server

[@ByteMonk]

@@ahamedkaize1634 In your use case, it sounds like you want to ensure that traffic from the users' home routers is able to reach the destination server by routing it through a reverse proxy server with a fixed public IP address. This way, the traffic will appear to be originating from the proxy server's IP address, which can be whitelisted on the destination server.
To achieve this, you can configure the reverse proxy server to route all traffic to the destination server, and then configure the destination server to only accept traffic from the proxy server's IP address.