{"id":41,"date":"2026-10-02T16:48:00","date_gmt":"2026-10-02T16:48:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/02\/rate-limiting-token-bucket-sliding-window\/"},"modified":"2026-10-02T16:48:00","modified_gmt":"2026-10-02T16:48:00","slug":"rate-limiting-token-bucket-sliding-window","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/02\/rate-limiting-token-bucket-sliding-window\/","title":{"rendered":"Rate Limiting Sadece &#8220;Dakikada 100 \u0130stek&#8221; Demek De\u011fildir"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir API&#8217;ye rate limit eklemek genellikle tek sat\u0131rl\u0131k bir gereksinim olarak gelir:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131 ba\u015f\u0131na dakikada 100 istek.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Kula\u011fa net geliyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama uygulamaya ba\u015flad\u0131\u011f\u0131n\u0131zda sorular \u00e7o\u011fal\u0131r. Dakika nerede ba\u015fl\u0131yor? Kullan\u0131c\u0131 kim? Birden fazla instance varsa saya\u00e7 nerede tutuluyor? Limit a\u015f\u0131ld\u0131\u011f\u0131nda ne d\u00f6n\u00fcl\u00fcyor?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fixed window<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">En basit y\u00f6ntem her dakika i\u00e7in bir saya\u00e7 tutmakt\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>key: rate:user:42:202610021948\nINCR \u2192 37\nEXPIRE 60<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Saya\u00e7 100&#8217;\u00fc ge\u00e7erse istek reddedilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Problemi pencere s\u0131n\u0131rlar\u0131nda ortaya \u00e7\u0131kar. Kullan\u0131c\u0131 19:48:59&#8217;da 100 istek, 19:49:00&#8217;da tekrar 100 istek g\u00f6nderebilir. \u0130ki saniye i\u00e7inde 200 istek. Limit ka\u011f\u0131t \u00fczerinde korunmu\u015f ama backend iki kat\u0131 y\u00fck alm\u0131\u015ft\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sliding window<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu s\u0131n\u0131r problemini azaltmak i\u00e7in son 60 saniyeye bak\u0131l\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her iste\u011fin zaman damgas\u0131n\u0131 bir sorted set i\u00e7inde tutmak en do\u011fru sonucu verir ama y\u00fcksek trafikte bellek maliyeti ciddi olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pratikte daha \u00e7ok kullan\u0131lan y\u00f6ntem iki pencereyi a\u011f\u0131rl\u0131kland\u0131rmakt\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>estimate = current_count\n         + previous_count \u00d7 (1 - elapsed_ratio)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nceki dakikada 80 istek, mevcut dakikan\u0131n %25&#8217;i ge\u00e7mi\u015f ve \u015fu ana kadar 30 istek varsa tahmini de\u011fer <code>30 + 80 \u00d7 0.75 = 90<\/code> olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kesin de\u011fildir ama yeterince iyidir. Cloudflare da kendi rate limiting yakla\u015f\u0131m\u0131n\u0131 anlat\u0131rken bu t\u00fcr bir yakla\u015f\u0131m\u0131n ger\u00e7ek trafikte \u00e7ok d\u00fc\u015f\u00fck hata oran\u0131yla \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan bahsediyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Token bucket<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Benim en s\u0131k tercih etti\u011fim model bu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir kova d\u00fc\u015f\u00fcn\u00fcn. Belirli bir h\u0131zla token ile dolar, belirli bir kapasitesi vard\u0131r. Her istek bir token harcar. Token yoksa istek reddedilir.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>capacity = 20\nrefill   = 10 token \/ saniye<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bu model iki \u015feyi ayr\u0131 ayr\u0131 ifade edebiliyor: ortalama h\u0131z ve izin verilen ani art\u0131\u015f.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131 bir s\u00fcre sessiz kald\u0131ysa kova dolar ve k\u0131sa bir burst&#8217;e izin verilir. S\u00fcrekli y\u00fcksek h\u0131zda istek g\u00f6nderirse refill h\u0131z\u0131na sabitlenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ger\u00e7ek kullan\u0131c\u0131 davran\u0131\u015f\u0131 da genellikle b\u00f6yledir. Sayfa a\u00e7\u0131ld\u0131\u011f\u0131nda birka\u00e7 istek ayn\u0131 anda gider, sonra sessizlik olur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Saya\u00e7 nerede tutulacak?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Tek instance&#8217;ta memory yeterli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Birden fazla instance varsa her biri kendi sayac\u0131n\u0131 tutarsa limit fiilen instance say\u0131s\u0131yla \u00e7arp\u0131l\u0131r. Bu y\u00fczden saya\u00e7 genellikle Redis gibi payla\u015f\u0131lan bir yerde tutulur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burada atomiklik \u00f6nemlidir. \u00d6nce okuyup sonra yazmak race condition olu\u015fturur. Token bucket mant\u0131\u011f\u0131n\u0131 tek bir Lua script i\u00e7inde \u00e7al\u0131\u015ft\u0131rmak bu problemi ortadan kald\u0131r\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>local tokens = redis.call('HGET', key, 'tokens')\n-- refill hesapla, token d\u00fc\u015f, kaydet<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bir de \u015fu karar verilmeli: Redis eri\u015filemez oldu\u011funda ne olacak? Fail-open m\u0131, fail-closed m\u0131?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7o\u011fu public API i\u00e7in rate limiter&#8217;\u0131n \u00e7\u00f6kmesi t\u00fcm API&#8217;yi durdurmamal\u0131. Ama login veya OTP gibi brute force&#8217;a a\u00e7\u0131k endpoint&#8217;lerde fail-closed daha do\u011fru bir tercih olabilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kime limit uyguluyoruz?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;Kullan\u0131c\u0131 ba\u015f\u0131na&#8221; ifadesi her endpoint i\u00e7in ayn\u0131 anlama gelmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Login endpoint&#8217;inde kullan\u0131c\u0131 hen\u00fcz belli de\u011fildir. IP adresi kullan\u0131labilir ama ayn\u0131 ofisten veya mobil operat\u00f6r NAT&#8217;\u0131 arkas\u0131ndan gelen y\u00fczlerce kullan\u0131c\u0131 ayn\u0131 IP&#8217;yi payla\u015fabilir. Bu durumda IP ve hedef hesap kombinasyonu daha anlaml\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Baz\u0131 endpoint&#8217;ler di\u011ferlerinden \u00e7ok daha pahal\u0131d\u0131r. Rapor \u00fcreten bir endpoint ile profil okuyan endpoint ayn\u0131 maliyeti ta\u015f\u0131maz. \u0130stek say\u0131s\u0131 yerine maliyet a\u011f\u0131rl\u0131\u011f\u0131 kullanmak burada i\u015fe yarar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Reddederken iyi davranmak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Limit a\u015f\u0131ld\u0131\u011f\u0131nda <code>429 Too Many Requests<\/code> d\u00f6nmek standartt\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama client&#8217;a ne zaman tekrar deneyebilece\u011fini s\u00f6ylemek de \u00f6nemlidir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>HTTP\/1.1 429 Too Many Requests\nRetry-After: 12\nRateLimit-Limit: 100\nRateLimit-Remaining: 0<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>Retry-After<\/code> olmadan client ne yapaca\u011f\u0131n\u0131 bilmez ve genellikle hemen tekrar dener. Bu da rate limiter&#8217;\u0131n engellemeye \u00e7al\u0131\u015ft\u0131\u011f\u0131 y\u00fck\u00fc yeniden \u00fcretir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rate limiting bir koruma mekanizmas\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama iyi tasarland\u0131\u011f\u0131nda ayn\u0131 zamanda API&#8217;nin client&#8217;larla yapt\u0131\u011f\u0131 bir s\u00f6zle\u015fme.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Fixed window, sliding window, token bucket. Rate limiting algoritmas\u0131n\u0131 se\u00e7mek kadar limitin kime, nerede ve nas\u0131l uygulanaca\u011f\u0131 da \u00f6nemli. Pratik bir bak\u0131\u015f.<\/p>\n","protected":false},"author":1,"featured_media":40,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-41","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-api-tasarimi"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/41","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=41"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/41\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/40"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=41"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=41"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=41"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}