missing section on quality of service and rate limits ?

[julienlau]

Hi,
Thanks for sharing this documentation.
I am bit surprised that there is nothing related to quality of services ?
Don't you consider rate limiting as something required out of the box for any API ?

Regards

[tkrop]

@julienlau sorry for the late reply.

Yes, we intentionally left out service operation aspects, when we created this API guideline over 8 years ago, and concentrated on the technical aspects that need to be included in the API. So we just created rules like #153 to defining technical how a rate limit must be specified and added a section about performance aspects. In the last years we started to add best practice tips where we saw value, but this up-to-now does not include quality-of-service.

May be the reason for this is, that we are using our own ingress router Skipper, which allows us to simply configure rate-limits for our services while our own Kubernetes on AWS takes care to scale our micro-services smoothly.