Max API's Count

Questions
1

BetterCloud interfaces with many external SaaS applications on behalf of our customers. We would like to use Kong as a rate limiting infrastructure piece between our microservices and the external SaaS apps. We thought about creating an API for each SaaS application, e.g. google-rl-api, slack-rl-api, dropbox-rl-api.

However, some of the SaaS apps use a custom sub domain per customer, e.g. https://bettercloud.slack.com. Since Kong does not support dynamic upstream urls, we would need to configure an API for each custom sub domain.

Is there a better approach, or is it ok to create 200 API’s? 500 API’s? 1000? 5000? We expect this problem to continue to grow. Is Kong the correct solution? Or should we investigate another tool?

2

Kong can handle those numbers. But depending on the exact data/structure a custom plugin might be more efficient.

3

Good to know. We are probably going to end up using a custom plugin. There are still more details to iron out on our side, but the solution will probably end up in a blog post at some point.

Thanks again for the feedback

4

How about using wildcard hosts?

5

Thanks for the suggestion. I was under the impression that we needed to set a static upstream url. I tried the following using “preserve host”:

Hosts: jsonplaceholder.typicode.com,*.jsontest.com
Upstream Url: http://jsonplaceholder.typicode.com
Preserve Host: true

curl http://localhost:8000/ -H "Host: ip.jsontest.com"
curl http://localhost:8000/ -H "Host: headers.jsontest.com"

It appears that it is attempting to resolve the correct host but the DNS cannot resolve through curl or postman.

Am I doing something wrong with wildcards or preserve host?