I came across your articles a few days ago and I find those very interesting and informative. A friendly feedback; can you please provide the full name of the acronyms when you first use them? Afterwards you can use the acronym in the following parts of the article. Therefore the reader does not need to open another browser in mobile to search what it is. It is really time consuming. For example not every reader can know VPS (including me-;))
It doesn't affect the client at all. You just use one IP address.
As far as I know, under the hood, they use virtual IP addresses. So all instances of the load balancer share the same virtual IP. And there's a thing called anycast routing. I'm not sure how it works, but many providers use this as well.
From our perspective, having one load balancer instance or 10 makes no difference.
I came across your articles a few days ago and I find those very interesting and informative. A friendly feedback; can you please provide the full name of the acronyms when you first use them? Afterwards you can use the acronym in the following parts of the article. Therefore the reader does not need to open another browser in mobile to search what it is. It is really time consuming. For example not every reader can know VPS (including me-;))
Good idea, thanks for the feedback!
You stated creating mutliple nodes of load balance on digital ocean.
How can this be managed in the client side, would they now have mutliple ips or base url to use?
What does this mean for a client trying to access the app/api.
It doesn't affect the client at all. You just use one IP address.
As far as I know, under the hood, they use virtual IP addresses. So all instances of the load balancer share the same virtual IP. And there's a thing called anycast routing. I'm not sure how it works, but many providers use this as well.
From our perspective, having one load balancer instance or 10 makes no difference.
Alright, thank you