3 ms·
I’d be wary as a “young dev” to claim he misunderstands. It will become very obvious to you later why Apache and Nginx exist. A very very small example is:
by nofunsir 5y ago
I’d be wary as a “young dev” to claim he misunderstands.
It will become very obvious to you later why Apache and Nginx exist.
A very very small example is:
So you want multiple “apps” on the same server? How ya gonna bind to the same port, 443? How are you going to play nice with other apps? How are you going to keep up with security loopholes? Does your app and every other app need access to the private key?
There hasn’t been a mindset shift. You simply haven’t experienced the whole set.
Even super large apps such as Atlassian’s suite rely largely on a reverse proxy being in place of you don’t want to tell your users to use some random port.
These web servers are fast and powerful.
How do you think load balancing is accomplished?
- brundolf 5y ago> I’d be wary as a “young dev” to claim he misunderstands. I only meant they misunderstand what I myself am saying. There's no need to get combative. > Even super large apps such as Atlassian’s suite rely largely on a reverse proxy > How do you think load balancing is accomplished? If you read my original comment, I specifically carved out these cases as not being what I'm talking about: > Of course nginx is more than that- in my limited experience I mostly see it used as a static file server and/or reverse-proxy and/or load balancer.