👉 Continue with the Nginx Crash Course you were asking for with a simple real-life demo: th-cam.com/video/q8OleYuqntY/w-d-xo.html Also who spots the typo in the video? 😄🙈 ▬▬▬▬▬▬ How we at TWN can help you advance your IT career: ▬▬▬▬▬▬ 🚀 Truly master DevOps in this 6-month DevOps Bootcamp and apply it confidently at work: ► Download Free Demo Projects List: bit.ly/3TkjnW5 ► More Infos: bit.ly/3XgG5zp 🚀 OR Learn the complete Software Development Life Cycle by taking up all key roles in practice: ► More Infos: bit.ly/47hdE9c No fluff, no knowledge gaps guaranteed. ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬
Brilliant, thanks Nana! I don't work in Networks or IT but I'm a software engineer and we often end up assisting on outage calls where the problems typically lie outside my area of expertise. Videos like this (that are so clearly explained) are invaluable in helping me understand the general architecture of our services. (Well, some of them, anyway. Haha. It really varies between our mix of brand new and decades-old applications 😂)
Идеально, добавить нечего. Автор гений. Очень всё доходчиво, без воды, учтены все детали, всё объяснено. Стиль повествования приятный, голос располагающий к себе, примеры с чуваком и остальные просто вышка!
Thanks for explaining this in such a clear and engaging way, especially by setting up the story! The restaurant example is brilliant-I'll never forget the difference between proxy, reverse proxy, and load balancer now. Appreciate all the effort that went into making this video
It is very important give content without confusing topics with same context. Explaining about other load balancers in cloud providers is very important to deliver content very clearly with best practices in practically. Thank you
I wish you had this video out a few weeks earlier, it would have saved me many hours of reading, getting an understanding most of what was in this video. You had a few things that I didn't know about, mostly because I wasn't looking for them. But, now I know are few more things than I did 20 minutes ago.
Thank you always for your simplified explanations. I would like to see a tutorial on: 1. Bash scripting for cloud/devops Engineers 2. Linux for cloud/devops engineers 3. Linux networking for cloud/devops engineers Thank you :)
Thank you for this good summary and explanation. Regarding using two reverse proxies for additional featgures and security I think that current cloud-load balancers (like AWS Application LB) already offer a lot of the features like NGINX, e.g. SSL termination, URL Paths and request headers which in many cases make an internal LB obsolete.
I would like to add that cloud load balancers like AWS ALB has a feature ‘session stickyness’ which helps in session persistence, speaking of filtering through request headers and url paths would need more aws services to come into play. So I can conclude that your implementation constraints (time and budget) will define wether is good idea or not to duplicate load balancing operations.
Thanks for the video I really appreciate the effort in your videos and I had to watch the video 2 times to get a clear picture and the visual shield more light to it. Just a question. Can we say forward proxy = proxy meaning it sits on the client side while the reverse proxy sits on the server side?
Great video I can show people I work with, as someone in security though I cringe a bit when I hear things like "will scan for any threat/malware/virus" esp on something like a proxy which is likely doing quite targeted scanning, let alone that most proxies aren't even configured to scan malware by default (as far as I have seen - it was said as if it was 100% something it does).
Thanks Nana🎉, your videos helping me to reach next step to my Devops journey. I have one request can you please make one video on how to setup an SSL certificate for any website and Which one is the best aproch to create certificate and setup SSL.
The explanation in the video is a bit confusig, in the beginning, she described a firewall, not a proxy. A Forward Proxy is essentially hiding the IP of the client by doing the requst with its ip on behalf of the client. A reverse proxy on the other hand, is set up on server side and redirect the request to the correct internal service thus allows rhe server administrator to not expose any service on any port to the public as the reverse proxy will route a request based on used domain to an specified service. The reverse proxy itself has access to internal services with their ports, even if the service is not exposed to the public.
00:04 Proxies, reverse proxies, and load balancers are essential web components for handling large traffic and ensuring data security. 01:44 Proxy acts as a guard for internal network 03:26 Proxy, reverse proxy, and load balancer explained 05:06 Reverse proxies provide SSL encryption, security checks, caching, and logging functionality. 06:48 Reverse proxy provides intelligent load balancing and security 08:28 In Kubernetes cluster, Ingress controller handles internal routing, while cloud load balancer manages external traffic. 10:08 Engine X as a high-performance web server and reverse proxy with load balancing 11:47 Certified DevOps Practitioner Program Overview Crafted by Merlin AI.
I really enjoyed this video, as well as the "Full NGINX Tutorial - Demo Project with Node.js, Docker"! However, I have the same question about both: you mention that we need both the cloud provider's load balancer (e.g., AWS) and a reverse proxy load balancer (e.g., NGINX). While I understand the role of the reverse proxy from your examples, I’m unclear about the specific benefits of the cloud provider’s load balancer. What purpose does it serve if it always routes to the same reverse proxy, or is it meant to handle multiple reverse proxies? Could you please elaborate on why the cloud provider's load balancer is needed and perhaps provide a practical example? Thanks!!
Thanks for the great video, Nana. One question: in many books there is a "third" type of proxy called "transparent". From what I understand it seems that clients are "aware" of forward and reverse proxies (forwards, especially, as they require some sort of configuration on the client itself - something I have only done once, back in the day, from the "Internet option" in Internet Explorer), whether a transparent one is completely... well, transparent to the client. Can you please add your two cents on this? Thank you, and keep up with your great work!
The main difference is where they are placed. In front of the client machines (forward proxy) or in front of the backend servers (Reverse proxy). Reverse proxies have way more capabilities than forward proxies (SSL, Caching, etc).
My understanding is that a reverse proxy is a generic service sitting between clients and servers, effectively hiding the server's address. On top of it, if this service can also balance load across different servers, then it becomes a load balancer. On top of this, adding features like auth, monitoring and API management, you get an API gateway. So essentially an API gateway can also act as a load balancer and reverse proxy. For example, Kong, an API gateway, is built on top of nginx, a reverse proxy. proxy is a generic service sitting between clients and servers, effectively hiding the client's address.
Imagine both proxies "facing" each other. Following a request flow from client to backend, it seems for forward proxy the request is moving in forward-direction, while for the Reverse Proxy the request moves in reverse direction.
The explanation in the video is a bit confusig, in the beginning, she described a firewall, not a proxy. A Forward Proxy is essentially hiding the IP of the client by doing the requst with its ip on behalf of the client. A reverse proxy on the other hand, is set up on server side and redirect the request to the correct internal service thus allows rhe server administrator to not expose any service on any port to the public as the reverse proxy will route a request based on used domain to an specified service. The reverse proxy itself has access to internal services with their ports, even if the service is not exposed to the public.
I agree with you. It is not a good name at all. Incoming and outgoing proxy would be clearer. I know this "accepted" in the industry, but it is still bad naming.
This is awesome 👍. Could you please create a video about Gunicorn and its Threads. How does reverse proxy work with it? And also how can we add Nginx with Gunicorn. Thank you 🙏
Awesome content, thank you so much for all of this work!!! I have a question though, on the chapter "Are Cloud Load Balancer a replacement or addition? And Why?"... You explain that, in practice, one may use a load balancer (i.e. nginx) to balance loads within a private subnet, while an AWS load balancer handles public requests... But from the diagram, I do not understand how this AWS entry server works as a load balancer since it only connects to one machine. Does it mean a real situation involves several nginx reverse proxies?
Thank you Nana, is it possible for you to make a video in which we can create an application, go through creating kubernetes ingresses and pods and making configurations and security by using forward proxy and reverse proxy with AWS load balancer?
I have understood that the nginx ingress controller uses ingress resource to create the needed aws load balancer. So the controller itself does not handle traffic.
On the subject of cloud load balancers + reverse proxy, specifically on AWS, you could have a private Application Load Balancer (in a private subnet) and create a hosted zone on Route 53 with (alias) pointing to the private load balancer. Thereby, eliminating the need for 2 load balancers (public and private).
Im not super familiar with AWS, but if Route 53 is just DNS and the Application Load Balancer is private, how does the traffic get to it? Unless Route 53 also acts like a proxy in which case its back to 2 proxies?
@@benhook1013 Route 53 has both private and public hosted zones. Route 53 acts as a DNS but with extra features like aliases, traffic flow, etc. Yes, in this case Route 53 acts as a proxy. However, it's cheaper than having 2 load balancers. And also Route 53 is a global service and you don't have to worry about HA, etc.
Seeing that the cloud load balancer has just a single reverse proxy server to talk. Is it necessary to have them there or is it just a representation error. Does the use of cloud balancer entail having to scale the reverse proxies (ingress controller)?
Hi, I have a question, in AWS load balancer we can do path mapping. like for ex for /inventory it will go to inventory microservice. if this feature is already there, then why we should go for another reverse proxy as well, whereas it's already done while load balancing? @nana
HI, i am new to networking but for the case of AWS ALB, doesn't it have all the load balancing features shown for NGINX? Also correct me if im wrong, but having NGINX/cloudflare is still good practice due to their edge locations being better than aws cloudfront and content caching which improves latency?
Your passing over the biggest benefit of using Nginx as the reverse proxy, which is that it is the entry point to your private network, you cant have an external service like AWS or Cloudflare be the entry point to your internal network (although as I say that they probably offer a way to send traffic to your backend over a VPN...), this single (or reduced) entrypoint means you only have to heavily lock down a subset of your machines.
👉 Continue with the Nginx Crash Course you were asking for with a simple real-life demo: th-cam.com/video/q8OleYuqntY/w-d-xo.html
Also who spots the typo in the video? 😄🙈
▬▬▬▬▬▬ How we at TWN can help you advance your IT career: ▬▬▬▬▬▬
🚀 Truly master DevOps in this 6-month DevOps Bootcamp and apply it confidently at work:
► Download Free Demo Projects List: bit.ly/3TkjnW5
► More Infos: bit.ly/3XgG5zp
🚀 OR Learn the complete Software Development Life Cycle by taking up all key roles in practice:
► More Infos: bit.ly/47hdE9c
No fluff, no knowledge gaps guaranteed.
▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬ ▬▬▬▬▬▬
🌹
Porxy! 🤣🤣
What about videos explaining the Harness Platform for DevOps and CI/CD, etc.
Me 🙋♂I spotted the typo 🙂
Excellent explanation Nana. I always learn a lot with your videos. They have no equal.
Hi @TechworldNana, I want to do this course,
Brilliant, thanks Nana! I don't work in Networks or IT but I'm a software engineer and we often end up assisting on outage calls where the problems typically lie outside my area of expertise. Videos like this (that are so clearly explained) are invaluable in helping me understand the general architecture of our services. (Well, some of them, anyway. Haha. It really varies between our mix of brand new and decades-old applications 😂)
Thanks for sharing, really happy to hear my videos are helpful! :)
this 13 min video on reverse proxy / nginx make me understood things that i wasnt able to in the last 6 months
Идеально, добавить нечего. Автор гений. Очень всё доходчиво, без воды, учтены все детали, всё объяснено. Стиль повествования приятный, голос располагающий к себе, примеры с чуваком и остальные просто вышка!
soglasen
Thanks!
Thanks for the support! :)
Thanks
13 mins completely Glued to the video, I appreciate your hard work
Thanks for explaining this in such a clear and engaging way, especially by setting up the story! The restaurant example is brilliant-I'll never forget the difference between proxy, reverse proxy, and load balancer now.
Appreciate all the effort that went into making this video
Thank you for your appreciation and nice words! :) Really happy you found the restaurant analogy useful!
A really good video for those new to IT Administration. Or for people who just want to understand the Infrastructer of the Internet.
Great video, simply explained!
your videos are very informative and no non-sense talking, to the point and clear with solid examples, keep it up, Thanks and Bless you
It is very important give content without confusing topics with same context. Explaining about other load balancers in cloud providers is very important to deliver content very clearly with best practices in practically. Thank you
Nana your content is so great! Thank you and keep going! With your videos I literally went from zero to hero !
I wish you had this video out a few weeks earlier, it would have saved me many hours of reading, getting an understanding most of what was in this video. You had a few things that I didn't know about, mostly because I wasn't looking for them. But, now I know are few more things than I did 20 minutes ago.
Nana, you are just a talented teacher. Well explained and understandable. Thank you so much!
You are naturally talanted. Thanks for this clear explanation
The best video about Proxy and Load Balancers
Excellent explanation! Very good quality content both for beginners and not)
Outstanding teacher as usual. thanks Nana
As usual ! Great content with such an amazing presentatation 😀 thanks
This was unimaginably useful, thanks a bunch!
Thank you always for your simplified explanations.
I would like to see a tutorial on:
1. Bash scripting for cloud/devops Engineers
2. Linux for cloud/devops engineers
3. Linux networking for cloud/devops engineers
Thank you :)
Many thanks and great suggestions I will definitely consider! 😊
The third one is a must! It would be very much appreciated
Thanks for such a simple and elegant explanation 🙂
This was amazing! I'm glad to have watched this!
thank u
very good explanation
i think the load balancing thing really helps me to remember what a reverse proxy is
Big fan nana, following you for years ❤🖤
Too good and made simple explanation Nana. Thanks for the new tech videos.
Very helpful as usual 😁 Thanks very much Nana
Thank you for this good summary and explanation. Regarding using two reverse proxies for additional featgures and security I think that current cloud-load balancers (like AWS Application LB) already offer a lot of the features like NGINX, e.g. SSL termination, URL Paths and request headers which in many cases make an internal LB obsolete.
Thank you for the invaluable contribution to IT. I am waiting for end to end course on MLOPS or AIOPS from you.
Excellent as always! Thank you!
I would like to add that cloud load balancers like AWS ALB has a feature ‘session stickyness’ which helps in session persistence, speaking of filtering through request headers and url paths would need more aws services to come into play. So I can conclude that your implementation constraints (time and budget) will define wether is good idea or not to duplicate load balancing operations.
Very well explained, Thank you! 👍🏻
❤ the explanation. Thanks a lot Nana
Great explanations
Thanks for the awesome explanation!
Thank you Nana :) The metaphors always help
Thanks for very good explanation
Good experience thank you so much Nana 😊
Once again a fabulous video.
Hello, I love the way you teach Thank you!! Q. I couldn't find the Java lesson
Thanks for the video I really appreciate the effort in your videos and I had to watch the video 2 times to get a clear picture and the visual shield more light to it.
Just a question. Can we say forward proxy = proxy meaning it sits on the client side while the reverse proxy sits on the server side?
Thank you, Nana! Great video, I learned a lot. Could you please make one on API Gateway?
As always an amazing job Nana
Thanks for your great feedback, happy to hear!
Awesome skill 👏
As excellent as ever
I wish I had found you earlier. Grateful.
Wow! Fantastic video! Thank you!
Glad you like it! :)
You're great 👍 nana❤
Thanks a lot.
I love how you explain your videos
Thanks for the session!
Thank you for the more informative video.
Great video I can show people I work with, as someone in security though I cringe a bit when I hear things like "will scan for any threat/malware/virus" esp on something like a proxy which is likely doing quite targeted scanning, let alone that most proxies aren't even configured to scan malware by default (as far as I have seen - it was said as if it was 100% something it does).
Thanks Nana🎉, your videos helping me to reach next step to my Devops journey. I have one request can you please make one video on how to setup an SSL certificate for any website and Which one is the best aproch to create certificate and setup SSL.
very excellent content , thanks!
Please make a video on rabbitMQ message queue service
Thanks for the suggestion!
Thank you for such good explanation!
hi im new here thank for amazing presentation you got my sub ❤
❤❤❤ ur Content
it's correct to say that in the k8's case the aws load balancer is the entrpoint node of the cluster of kubernetes? probably i am confused
The explanation in the video is a bit confusig, in the beginning, she described a firewall, not a proxy.
A Forward Proxy is essentially hiding the IP of the client by doing the requst with its ip on behalf of the client.
A reverse proxy on the other hand, is set up on server side and redirect the request to the correct internal service thus allows rhe server administrator to not expose any service on any port to the public as the reverse proxy will route a request based on used domain to an specified service. The reverse proxy itself has access to internal services with their ports, even if the service is not exposed to the public.
Great explanation, thank you! :)
Thank you for the explanation!
thank u a lot for this insightfull information it was very helpful
you are incredible
00:04 Proxies, reverse proxies, and load balancers are essential web components for handling large traffic and ensuring data security.
01:44 Proxy acts as a guard for internal network
03:26 Proxy, reverse proxy, and load balancer explained
05:06 Reverse proxies provide SSL encryption, security checks, caching, and logging functionality.
06:48 Reverse proxy provides intelligent load balancing and security
08:28 In Kubernetes cluster, Ingress controller handles internal routing, while cloud load balancer manages external traffic.
10:08 Engine X as a high-performance web server and reverse proxy with load balancing
11:47 Certified DevOps Practitioner Program Overview
Crafted by Merlin AI.
As a old fashioned system manager, we are using apache as forward-reverse proxy server. Nginx is being populer rather than apache as ı can see.
I really enjoyed this video, as well as the "Full NGINX Tutorial - Demo Project with Node.js, Docker"!
However, I have the same question about both: you mention that we need both the cloud provider's load balancer (e.g., AWS) and a reverse proxy load balancer (e.g., NGINX).
While I understand the role of the reverse proxy from your examples, I’m unclear about the specific benefits of the cloud provider’s load balancer. What purpose does it serve if it always routes to the same reverse proxy, or is it meant to handle multiple reverse proxies?
Could you please elaborate on why the cloud provider's load balancer is needed and perhaps provide a practical example?
Thanks!!
thanks clearly explained
Hello 👋 Nana - thank you for this video. Question: Does the Reverse Proxy use Consistent Hashing or the Cloud Load Balancer or both?
Thank you for doing this!
Thanks for the great video, Nana.
One question: in many books there is a "third" type of proxy called "transparent". From what I understand it seems that clients are "aware" of forward and reverse proxies (forwards, especially, as they require some sort of configuration on the client itself - something I have only done once, back in the day, from the "Internet option" in Internet Explorer), whether a transparent one is completely... well, transparent to the client. Can you please add your two cents on this?
Thank you, and keep up with your great work!
good job 😍
Still dont get it, why its called "reverse" proxy. It does nothing reverse. It does the same thing in a network as the proxy.
The main difference is where they are placed. In front of the client machines (forward proxy) or in front of the backend servers (Reverse proxy). Reverse proxies have way more capabilities than forward proxies (SSL, Caching, etc).
My understanding is that a reverse proxy is a generic service sitting between clients and servers, effectively hiding the server's address. On top of it, if this service can also balance load across different servers, then it becomes a load balancer. On top of this, adding features like auth, monitoring and API management, you get an API gateway.
So essentially an API gateway can also act as a load balancer and reverse proxy. For example, Kong, an API gateway, is built on top of nginx, a reverse proxy.
proxy is a generic service sitting between clients and servers, effectively hiding the client's address.
Imagine both proxies "facing" each other. Following a request flow from client to backend, it seems for forward proxy the request is moving in forward-direction, while for the Reverse Proxy the request moves in reverse direction.
The explanation in the video is a bit confusig, in the beginning, she described a firewall, not a proxy.
A Forward Proxy is essentially hiding the IP of the client by doing the requst with its ip on behalf of the client.
A reverse proxy on the other hand, is set up on server side and redirect the request to the correct internal service thus allows rhe server administrator to not expose any service on any port to the public as the reverse proxy will route a request based on used domain to an specified service. The reverse proxy itself has access to internal services with their ports, even if the service is not exposed to the public.
I agree with you. It is not a good name at all. Incoming and outgoing proxy would be clearer.
I know this "accepted" in the industry, but it is still bad naming.
Hi Nana. Your videos explain very good. Do you have videos that teach the details of Nginx configuration and HTTPS configuration?
Thank you for the information can you make a video about azure front door and functionalities
This is awesome 👍. Could you please create a video about Gunicorn and its Threads. How does reverse proxy work with it? And also how can we add Nginx with Gunicorn. Thank you 🙏
Cool, thanks!
My pleasure :)
Thank you ❤
Awesome content, thank you so much for all of this work!!! I have a question though, on the chapter "Are Cloud Load Balancer a replacement or addition? And Why?"... You explain that, in practice, one may use a load balancer (i.e. nginx) to balance loads within a private subnet, while an AWS load balancer handles public requests... But from the diagram, I do not understand how this AWS entry server works as a load balancer since it only connects to one machine. Does it mean a real situation involves several nginx reverse proxies?
Super helpful ...hey nana can u make a video on rpc.Thanks
Thank you Nana, is it possible for you to make a video in which we can create an application, go through creating kubernetes ingresses and pods and making configurations and security by using forward proxy and reverse proxy with AWS load balancer?
Brilliant
Thank you - Question: HAProxy is reverse proxy OR a kind of Load Balancer ?
The sound is perfect
Thank you for confirming 🙏
I have understood that the nginx ingress controller uses ingress resource to create the needed aws load balancer. So the controller itself does not handle traffic.
This is a great video. Thanks. ^_^
On the subject of cloud load balancers + reverse proxy, specifically on AWS, you could have a private Application Load Balancer (in a private subnet) and create a hosted zone on Route 53 with (alias) pointing to the private load balancer.
Thereby, eliminating the need for 2 load balancers (public and private).
Im not super familiar with AWS, but if Route 53 is just DNS and the Application Load Balancer is private, how does the traffic get to it? Unless Route 53 also acts like a proxy in which case its back to 2 proxies?
@@benhook1013 Route 53 has both private and public hosted zones.
Route 53 acts as a DNS but with extra features like aliases, traffic flow, etc.
Yes, in this case Route 53 acts as a proxy. However, it's cheaper than having 2 load balancers. And also Route 53 is a global service and you don't have to worry about HA, etc.
Seeing that the cloud load balancer has just a single reverse proxy server to talk. Is it necessary to have them there or is it just a representation error. Does the use of cloud balancer entail having to scale the reverse proxies (ingress controller)?
can you tell me what is the tool you are using to make these diagrams?
quuite insightful
Hi, I have a question, in AWS load balancer we can do path mapping. like for ex for /inventory it will go to inventory microservice. if this feature is already there, then why we should go for another reverse proxy as well, whereas it's already done while load balancing? @nana
Thank you
You're welcome :)
What tool do u use to prepare ur presentations ?
Wow, more simply explained for security topics also will be more interesting.
HI, i am new to networking but for the case of AWS ALB, doesn't it have all the load balancing features shown for NGINX?
Also correct me if im wrong, but having NGINX/cloudflare is still good practice due to their edge locations being better than aws cloudfront and content caching which improves latency?
Your passing over the biggest benefit of using Nginx as the reverse proxy, which is that it is the entry point to your private network, you cant have an external service like AWS or Cloudflare be the entry point to your internal network (although as I say that they probably offer a way to send traffic to your backend over a VPN...), this single (or reduced) entrypoint means you only have to heavily lock down a subset of your machines.
Cloud balancer can also direct request based on the url path, so it's not correct that we need reverse proxy for advanced routing and sticky session
Thank you Nana. So proxy is like Firewall in our computer. Isn't it?
thank you : )
😁😁 thank you