Proxy is the word we hear a lot. In the English dictionary, it means a substitute — providing the power of authority to act like the one. In the computing world, a proxy means a middleman between a client and a server. A client originates a request which is received by the middleman who then transfers it to a server for the data and then goes to the middleman again before the client receives it. The middleman here is a proxy.
The proxy servers are very useful when you design a system. The principle of VPNs is based on proxy. When you use a proxy, it can sometimes mask the identity of a client which leads to having the IP address of the proxy in the server instead of the originating client itself. We might have experienced this in this while we access the restricted data or try to download things via torrent.
When we use the word proxy, we usually mean ‘forward proxy’. It is the proxy that acts on the behalf of the client while the interaction between the client and the server is made. This is different than the ‘reverse proxy’ which acts on the behalf of the server. The data flow or the diagram — all look the same.
Client ⬅️➡️ Proxy ⬅️➡️ Server
But how do distinguish between ‘forward proxy’ and ‘reverse proxy’?
If the server is unknown about the client’s request and its response traveling via the proxy, it’s a forward proxy. But, if the client is unknown about the request and response via the proxy, it’s a reverse proxy. This makes the whole ideology behind the proxy sneaky.
Conclusion
When you are up for designing a system, proxies might be a life savior. Especially, the reverse proxies. It can act like a gatekeeper or a screener or a load-balancer or an all-around assistant. If you don’t want your main server handling some minor tasks, it might be passed on to the proxies.
So, it is important to understand the reason for the existence of the proxies while also knowing what they do.
pragyaasapkota
/
System-Design-Concepts
A repo with some system design concepts.
System Design
Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements.
This is a index for the concepts of system.
If you wish to open these in a new tab, Press CTRL+click
| S.N. | Table of Content |
|---|---|
| 1. | Caching |
| 2. | Network Protocols |
| 3. | Storage: The Underrated Topic |
| 4. | Latency and Throughput |
| 5. | System Availability |
| 6. | Leader Election |
| 7. | Proxies |
| 8. | Load Balancing |
| 9. | Endpoint Protection |
| 10. | HTTPS: Is it better than HTTP? |
| 11. | Polling and Streaming |
| 12. | Long Polling |
| 13. | Hashing |
| 14. | CAP Theorem |
| 15. | PACELC Theorem |
| 16. | Messaging and Pub-Sub |
| 17. | Database |
| 18. | Logging, Monitoring, and Alerting |
| 19. | Distributed System |
| 20. | Scaling |
| 21. | Event Driven Architecture (EDA) |
Thank you!!!
I hope this article was helpful to you.
Please don’t forget to follow me!!!
Any kind of feedback or comment is welcome!!!
Thank you for your time and support!!!!
Keep Reading!! Keep Learning!!!
Top comments (0)