all ports 9001 ,9002 and 9003 pointing to different project path, my question, can we point to same project folder path? does pointing to same folder path cause performance degradation?
Is there any way to make the load balancer not be the single point of failure ?? If it goes down, all the healthy machines and services become useless right ??
Im using Nginx for loadbalancing my 4 server setup for a custom application. The application has a media share option that if disabled the forward option does not allow people from other networks to see it. It uses the IP of the user for this. The problem is if i use load balancing all the hits to my web server are coming from the load balancers IP. So even if a user from external network tries to access the media after disabling that option, he is able to access the media because server is getting the IP of Nginx setup. Is there any feature to overcome this issue?
Thank you for the video. In studying the Nginx Cook-Book and trying to further understand the "hash directive" from this video, it's not 100% clear how it works. Do I create a hash of the specific data I want to match and if it's "anywhere" in the request, then it goes to a specific server? Or do I have to create a hash of the entire "request" I'm looking to match? Any help in this area is greatly appreciated. 🙏
I think, I understand it a little bit better (after digesting content from different sources on this subject). I don't create the hash, I simply provide the data that "may" be in a specific request I'm trying to match and want forwarded to a specific server. Nginx does the hashing of every request using the data I provided and if a request matches that hash, then the request goes to the server that request session originated from? I presume, it requires the administrator to be familiar with the structure of the requests he/she is trying to match against, in addition to what kind of data might be in those requests, to use the "generic hash" directive effectively. Anyway, thanks youtube comment section for being my rubber ducky! :P
Links:
NGINX Configuration Context: ua-cam.com/video/C5kMgshNc6g/v-deo.html
NGINX Reverse Proxy: ua-cam.com/video/lZVAI3PqgHc/v-deo.html
Jay is the man! Thank you.
Great to see nice demo explanation. 👍
Glad you liked it!
thanks for this training, it was very good
Amazing explanation!
This was a great explanation!
all ports 9001 ,9002 and 9003 pointing to different project path, my question, can we point to same project folder path? does pointing to same folder path cause performance degradation?
My gosh it was a great explanation !
Is there any way to make the load balancer not be the single point of failure ?? If it goes down, all the healthy machines and services become useless right ??
From VietNam. Thanks
Im using Nginx for loadbalancing my 4 server setup for a custom application. The application has a media share option that if disabled the forward option does not allow people from other networks to see it. It uses the IP of the user for this. The problem is if i use load balancing all the hits to my web server are coming from the load balancers IP. So even if a user from external network tries to access the media after disabling that option, he is able to access the media because server is getting the IP of Nginx setup. Is there any feature to overcome this issue?
Thank you. great demo.
Thanks for the helpful session.
please note that sticky session is not free, it come with nginx plus
Love the explanation, hate the indentations.
Workload I need load-balanced is VOIP streamed via UDP. Can NGINX Open Source forward UDP or it needs to be Plus?
this very good catch, thank you Sir!
thank for teaching
Thank you for the video. In studying the Nginx Cook-Book and trying to further understand the "hash directive" from this video, it's not 100% clear how it works. Do I create a hash of the specific data I want to match and if it's "anywhere" in the request, then it goes to a specific server? Or do I have to create a hash of the entire "request" I'm looking to match? Any help in this area is greatly appreciated. 🙏
I think, I understand it a little bit better (after digesting content from different sources on this subject). I don't create the hash, I simply provide the data that "may" be in a specific request I'm trying to match and want forwarded to a specific server. Nginx does the hashing of every request using the data I provided and if a request matches that hash, then the request goes to the server that request session originated from? I presume, it requires the administrator to be familiar with the structure of the requests he/she is trying to match against, in addition to what kind of data might be in those requests, to use the "generic hash" directive effectively. Anyway, thanks youtube comment section for being my rubber ducky! :P
It's a very nice presentation..
Good work Jay!
very useful, thanks
These three web servers still share one physical server right?
thank you , amazing content
I cant see,increase font size on no.20
This LB isn't DSR (Direct server return) or is it? 🤨
And can nginx do such LB?
Great video
Think you
Why wouldn’t you demo this with SSL?
HA for nginx ? How to do that .
Awesome video ++++++++++++ 🙂
is there a way to install a web GUI to administer the load balancer?
15:48 You need to pay for that.
Epic explanation.. made it very easy.
Thanks!
Could you add the links you mentioned in the video?
Thanks Felix. The links are included in the "GitHub Repo" like included with the comments. github.com/jay-nginx/load-balancing
9oo
9op
Izin belajar pak
No sir. Linux (Ubuntu) has a built- in and much easier and secure way to load balance
Oww so the correct way to call it is engine X. I was mistaken my whole life.
please i need to contact you