Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

RATE_LIMITER_POLICY

Also known as

rate_limiter_policy, rate_limiter (with or without @ prefix)

Apply a rate limiting policy to the endpoint. The policy name must match a policy configured in the Rate Limiter configuration.

Syntax

@rate_limiter_policy <policy-name>
@rate_limiter <policy-name>

Examples

Fixed Window Policy

Apply a fixed window rate limiter to an API endpoint:

sql
comment on function public_api() is
'HTTP GET
@rate_limiter_policy fixed';

With configuration:

json
{
  "RateLimiterOptions": {
    "Enabled": true,
    "Policies": [
      {
        "Type": "FixedWindow",
        "Enabled": true,
        "Name": "fixed",
        "PermitLimit": 100,
        "WindowSeconds": 60
      }
    ]
  }
}

Token Bucket Policy

Apply a token bucket rate limiter to an expensive operation:

sql
comment on function expensive_operation() is
'HTTP POST
@rate_limiter bucket';

With configuration:

json
{
  "RateLimiterOptions": {
    "Enabled": true,
    "Policies": [
      {
        "Type": "TokenBucket",
        "Enabled": true,
        "Name": "bucket",
        "TokenLimit": 10,
        "ReplenishmentPeriodSeconds": 60
      }
    ]
  }
}

Combined with Authorization

Apply rate limiting to an authenticated endpoint:

sql
comment on function protected_resource() is
'HTTP GET
@authorize
@rate_limiter authenticated_limit';

With configuration:

json
{
  "RateLimiterOptions": {
    "Enabled": true,
    "Policies": [
      {
        "Type": "SlidingWindow",
        "Enabled": true,
        "Name": "authenticated_limit",
        "PermitLimit": 1000,
        "WindowSeconds": 60,
        "SegmentsPerWindow": 6
      }
    ]
  }
}

Behavior

  • The policy name must match the Name field of a policy defined in the Rate Limiter configuration
  • If the policy name doesn't match any configured policy, rate limiting won't be applied
  • Returns 429 Too Many Requests when limit exceeded (status code and message are configurable)
  • Policy defines requests per time window based on the policy type (FixedWindow, SlidingWindow, TokenBucket, or Concurrency)

Comments

Released under the MIT License.