Skip to content

Applying rate limit to Search

SHEFFALI JAIN requested to merge ratelimits into Azure/OSDU-Helm-Charts-Azure-M8-Master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

  • YES
  • NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • YES
  • NO

Scope and Context

We are trying to provide design via which rate limiting can be applied to any service if enabled via flag and will be disabled by default. By setting a limit on how many requests a consumer is allowed to make in a given unit of time. We reject any requests above the limit with an appropriate response, like HTTP status 429 (Too Many Requests).

What is the current behavior?

Currently, no rate limiting is applied on service which can limit the count of users accessing it.

What is the new/expected behavior?

The service will have specific token count which will set limit to restrict number of users using the service per cycle.

Have you added/updated Unit Tests and Integration Tests?

No.

Any other useful information

Added Envoy filter to apply rate limiting. Added support to generate yaml file via Helm in deployment itself. Initially value of applying rate limit filter is set to false. It can be set while installing helm command using following instruction : --set envoyFilter.enabled=true

Comments : !211 (closed)

Edited by SHEFFALI JAIN

Merge request reports