Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
The reverse proxy is frankly a "best practice" architecture, not just for security but also for resource limiting of your hard-working application server. Often the reverse proxy will communicate ...
Answer
#1: Initial revision
by
gbjbaanb
·
2023-10-22T23:14:00Z (about 1 year ago)
The reverse proxy is frankly a "best practice" architecture, not just for security but also for resource limiting of your hard-working application server. Often the reverse proxy will communicate using web protocols anyway, so you are reusing webserver comms for internal comms, which will often make the whole thing easier to implement. Most programming languages have webserver services or libraries available, its not really about using a dedicated webserver or using your app as a webserver, the reason is architectural. Forget the networking protocol, its about that security, rate limiting, load balancing and every other good thing you get from this architecture. Note that this is already happening when you "directly" connect a webserver to the web, it'll be behind all manner of routers, CDNs and NAT bridges to get the data to you.