You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kind like pub/sub but for HTTP. While we could use nginx with this config:
upstream multiple_upstream {
server host1
server host2
server host3
}
server {
location / {
proxy_pass http://multiple_upstream;
}
There are several drawbacks, like the fact nginx does the dns resolving once and only on the startup, so if one of the upstream servers is down nginx will refuse to start. Even worse, if you update the docker container of one of the upstreams and they do change the ip, nginx won’t be able to redirect requests to this new container, nor can it handle multiple containers/machines like treaefik does.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Kind like pub/sub but for HTTP. While we could use nginx with this config:
There are several drawbacks, like the fact nginx does the dns resolving once and only on the startup, so if one of the upstream servers is down nginx will refuse to start. Even worse, if you update the docker container of one of the upstreams and they do change the ip, nginx won’t be able to redirect requests to this new container, nor can it handle multiple containers/machines like treaefik does.
The text was updated successfully, but these errors were encountered: