Re:Beginners guide to gateways and proxies
by JoeAltmaier on Sunday April 26, 2020 @12:23PM
(#22988205)
Yes its a sad thing that as anything matures, the technical terms get washed out by the tide of amateurs entering the field. The wrong error codes get used; the wrong names get put on things (e.g. Chrome is an operating system instead of a desktop). We old geezers try to stand against the waves, but get washed away.
Re:Beginners guide to gateways and proxies
by game_the0ry on Sunday April 26, 2020 @01:05PM
(#22988478)
Hey old geezers - please keep old geez-ing. As a clueless amateur myself, I appreciate it when my elders set me straight. I need your wisdom.
Please don't be discouraged or lose hope on us, especially when our own hubris gets the better of us. We just don't know any better ... yet.
Re:Beginners guide to gateways and proxies
by koffiezet on Monday April 27, 2020 @12:13PM
(#22997192)
Something like an "API gateway" does a lot more than load balancing, and sometimes it doesn't even do any load balancing. Are you still going to call it a load-balancer? Gateway is a much better description.
In web applications frameworks you also have a 'router' concept, which is also a network thing. It doesn't mean that because the network thing happens to route traffic around that the router in the web application can't route requests to the correct code.
A gateway is a network device that gives access to other networks (usually the router giving you internet). A proxy is an intermediate system to access, filter and cache requests, usually HTTP requests to the internet, not to confuse with a reverse proxy / load balancer that doesn't do that.
Of course all these are related network equipments often managed by the same guys, so go figure what tickets about "device" are really about.
edit: Also, it should be returning 401 instead of 403. This reminds me I need to make a post about the good usage of 401 and 403.