How to scale docker containers using Nginx as reverse proxy and load balancer

In this video we will learn how to #scale #docker container using #Nginx as reverse proxy, this nginx reverse proxy would also act as a load balancer at the very same time.

For example I have used a very basic Nodejs Express application to demonstrate the same.

--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
💵Support the channel:
--------------------------------------------------------------------------
--------------------------------------------------------------------------

======================
✔ Other useful Playlists
======================

#yoursTRULY #tutorial #howto #nodejs

[suman]

Such crisp & clear explanation. Thanks a lot.

[aspirinemaga]

Man what a perfect and straight explanation. thank you so much for your efforts! you are a legend

[abhijeetshikharvlog]

Your docker series is awosme .Beacuse u covered almost all tpoics in crash code mode .Thanks

[petroniobonavides]

Mann.. this lecture is awesome.. thanks.

[mhavock]

Still waiting to see the 1000 container version as promised in the thumbnail .... :)

[teetanrobotics]

Please include this in the "Production ready server" playlist. As horizontal auto-scaling is also a very useful feature in the production ready server. Amazing content. Thanks.

[namcaohai]

thank you so much. All you guys are brilliant!!

[someonenotlikeyou]

I have been scratching my head the whole day trying to figure out why my nginx wasn't working. I wasn't using docker-compose.yml; instead, I was creating separate containers for each server instance. On top of that, I was editing the main nginx configuration file (/etc/nginx/nginx.conf) instead of changing the virtual host configuration file as you did.

After watching your video, I figured out two issues. First, my containers were not communicating with each other because I hadn't created a custom network for them. After doing that, everything worked fine with reverse proxy and load balancing. Second, I still don't understand what the issue was with using the same upstream to specify the servers and the location with the proxy_pass directive to send them to the servers in round-robin.

Maybe it's not a good practice to update the main nginx configuration file directly, but I'm not sure. Can you provide me with some resources to read more about nginx configurations? Thanks a lot; this video was a great help! 💕💕

[audiodrocher]

Please accept my gratitude for your content it's definitely helpful ☺️

[ilyaslabukarov]

Thank you very much!
This video helped me a lot.

[eddwinnas]

I couldnt figure it out and you saved me hours of work thanks!!!

[digvijayyamagekar]

this is some production level content 😂
thanks man

[mehmetbilentr]

Simple and quite usefull explanation, thank you.

[riteshthakur]

Great tutorial sir as always you make really good tutorials.

[Mysterious_debris_]

Great content. Do upload similar content so that we as developers can get advanced.

[mukuljain]

great tutorial, bring more videos on how to work with nodejs and if possible react and aws

[vishaldharmawat]

Amazing Video :)
Really helped, just one correction, I believe CI stands for Clean Install. Please correct me if I am wrong.

[digvijaysinghthakur]

So clear and precise tutorial please make tutorials on kubernetes for beginners also.

[LexPrimost]

Hi ! great video as usual !, is that a normal behavior that you can access the api container by its port without exposing the 3000 port in its Dockerfile?

[kks]

Great explanation, thank you.
I was just wondering, if we are running in same machine we can use cluster module as well right?
The nginx with auto-scaling may become prominent when using multiple standalone servers, isn't that right?