Using reverse proxies as a substitute for routing tables?
Using reverse proxies as a substitute for routing tables?
I’m a complete beginner to nginx. We currently use routing tables and do IP based routing on our clients. We will enter the IP address of the database the client can connect to along with a port.
However, if the database goes down then the client can not connect to it. We have a failover set up but since it is IP based, we will have to manually change the IP address in the routing table.
Is there any way we can make it so that it’s perhaps DNS name based so that if the first database goes down it will hop over to the failover?
My apologies if what I’m asking is not even possible. I’m very new to all this but need to find a way we can do this. If there’s any solution it will be greatly appreciated. Thank you all in advance.
However, if the database goes down then the client can not connect to it. We have a failover set up but since it is IP based, we will have to manually change the IP address in the routing table.
Is there any way we can make it so that it’s perhaps DNS name based so that if the first database goes down it will hop over to the failover?
My apologies if what I’m asking is not even possible. I’m very new to all this but need to find a way we can do this. If there’s any solution it will be greatly appreciated. Thank you all in advance.
Re: Using reverse proxies as a substitute for routing tables?
Hi,
Try refer to this article: https://docs.nginx.com/nginx/admin-guid ... -balancer/
And this one too: https://severalnines.com/blog/using-ngi ... ra-cluster
Try refer to this article: https://docs.nginx.com/nginx/admin-guid ... -balancer/
And this one too: https://severalnines.com/blog/using-ngi ... ra-cluster