Apache APISIX vs KONG

Apache apisix benchmark script: https://github.com/iresty/apisix/blob/master/benchmark/run.sh

Kong beanchmark script: 

curl -i -X POST \
  --url http://localhost:8001/services/ \
  --data 'name=example-service' \
  --data 'host=127.0.0.1'

curl -i -X POST \
  --url http://localhost:8001/services/example-service/routes \
  --data 'paths[]=/hello'

curl -i -X POST http://localhost:8001/routes/efd9d857-39bf-4154-85ec-edb7c1f53856/plugins \
  --data "name=rate-limiting" \
  --data "config.hour=999999999999" \
  --data "config.policy=local"

curl -i -X POST http://localhost:8001/routes/efd9d857-39bf-4154-85ec-edb7c1f53856/plugins \
  --data "name=prometheus"

curl -i http://127.0.0.1:8000/hello/hello

wrk -d 5 -c 16 http://127.0.0.1:8000/hello/hello

@knysfh After doing a lot of tests, I decided to have everything directly on the server side without a reverse proxy and use native K8S capabilities + changes on the main server side. Resource utilisation and performance both improved in my testing.

Also the reason was that I don't want to many components, it makes everything harder to maintain.