Just because an app can serve a request does not mean it should. Nginx can handle requests at scale and also do asset caching.
Also, your questions at this point are extremely vague. You need to spend time determining exactly what you want to learn. Because unless you have a clear goal, you'll never progress. I'd start by researching how Nginx is used with whatever app you're using, and then start asking yourself questions like "why do this via Nginx instead of doing it with just the app?", then go find the answers to "why not use $app as the server." and get Nginx out of the mix, because the two are not directly related. Because where Nginx could be used, so could Apache + Passenger or some other stack.
> Also, your questions at this point are extremely vague.
I think the OP acknowledged that when they said more advanced topics whatever they might be.l and asked for suggestions for resources to learn from. Otherwise how should they know what they don’t know?
In answering the question, I too was vague. Point taken. I was referring to the nginx question specifically. And I tried maybe not hard enough to convey that there is a need to start chasing down one question at a time. Don't most journeys start that way?
Also, my suggestion to learn more about servers in general, which I didn't actually answer, is to build one. If the OP wants a link to how to build a LAMP stack, I can supply an article series I wrote on the subject some time back. It's a little out of date, but the concepts apply.
6 comments
[ 3.3 ms ] story [ 13.6 ms ] threadAlso, your questions at this point are extremely vague. You need to spend time determining exactly what you want to learn. Because unless you have a clear goal, you'll never progress. I'd start by researching how Nginx is used with whatever app you're using, and then start asking yourself questions like "why do this via Nginx instead of doing it with just the app?", then go find the answers to "why not use $app as the server." and get Nginx out of the mix, because the two are not directly related. Because where Nginx could be used, so could Apache + Passenger or some other stack.
I think the OP acknowledged that when they said more advanced topics whatever they might be.l and asked for suggestions for resources to learn from. Otherwise how should they know what they don’t know?
Also, my suggestion to learn more about servers in general, which I didn't actually answer, is to build one. If the OP wants a link to how to build a LAMP stack, I can supply an article series I wrote on the subject some time back. It's a little out of date, but the concepts apply.
- UNIX and Linux System Administration Handbook
- The Practice of System and Network Administration
- The Practice of Cloud System Administration
- Tannenbaum's textbooks (operating systems / networks)
- Readings in Database Systems