Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mauricioabreu/dynamic-upstream-learning
Playing with NGINX lua balancing features
https://github.com/mauricioabreu/dynamic-upstream-learning
Last synced: about 1 month ago
JSON representation
Playing with NGINX lua balancing features
- Host: GitHub
- URL: https://github.com/mauricioabreu/dynamic-upstream-learning
- Owner: mauricioabreu
- Created: 2023-06-08T14:43:31.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-06-10T13:20:49.000Z (over 1 year ago)
- Last Synced: 2024-04-17T22:17:48.344Z (7 months ago)
- Language: Dockerfile
- Size: 11.7 KB
- Stars: 4
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Dynamic Upstream learning
Just playing with some NGINX lua balancing features
## Motivation
I wanted to learn more about how to balance requests to upstreams in a more dynamic way. What if I need to route some requests to one upstream A, and some other requests to upstream B.
## Problem
You have given the task of balancing requests. If a request with `/foo/something` comes in you need to balance the requests between to server A (primary) and pick the server B (backup) when A does not work.
Ok, it could be a static upstream in NGINX, right? Yes, you are right but rabbits don't come easy.
Servers come and go, and we need to be ready to deliver different hosts for different requests.
```mermaid
sequenceDiagram
participant User
participant NGINX
participant Server1 as 127.0.0.2
participant Server2 as 127.0.0.3
User->>NGINX: Request /foo/something
NGINX->>Server1: Proxy Pass
Server1->>NGINX: Success Response
NGINX->>User: Forward Success Response
User->>NGINX: Request /foo/something
NGINX->>Server1: Proxy Pass
Server1-->>NGINX: Failure Response
NGINX->>Server2: Proxy Pass
Server2->>NGINX: Success Response
NGINX->>User: Forward Success Response
```
## Running
Dependencies:
* [just](https://github.com/casey/just)
* [docker compose](https://docs.docker.com/compose/)
```console
$ just -l
Available recipes:
rebuild # Rebuild all containers
reload # Reload NGINX
run # Start origin and upstreams API
stop # Stop origin and upstreams API
```
```console
$ just run
```
Now you have NGINX running on 8080 and upstreams API on 8081.
Go ahead and make a request for an existing upstream:
```
curl -v http://localhost:8080/upstream1/foo
```
Then for an upstream that does not exist:
```
curl -v http://localhost:8080/upstream2/foo
```
Compare the logs and the HTTP responses.