News KrakenD 2.3.3 (patch version) released


Recent changes

You are viewing a previous version of KrakenD Enterprise Edition (v2.0) , go to the latest version

Traffic management overview

Last update: Sep 29, 2018

KrakenD offers several ways to protect the usage of your infrastructure that might act at very different levels.

The most significant type of traffic management feature is the rate limit that allows you to throttle the traffic of end-users or the traffic of KrakenD against your backend services. The rate limits mainly cover the following purposes:

  • Avoid stressing or flooding your backend services with massive requests (proxy rate limit)
  • Establish a quota of usage for your exposed API (router rate limit)
  • Create a simple QoS strategy for your API

Traffic Management covers:

  • Circuit Breaker: An automatic protection measure for your stack and avoids cascade failures.
  • Rate-limiting:
  • Spike Arrest: Ensures a minimum time between different requests goes by
  • Service Discovery: To detect and locate services automatically on your enterprise network.
  • Bot detection: Reject bots carrying out scraping, content theft, and other forms of spam.

Unresolved issues?

The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.

We use cookies to understand how you use our site and to improve your overall experience. By continuing to use our site, you accept our Privacy Policy. More information