{"id":47,"date":"2026-10-08T18:57:00","date_gmt":"2026-10-08T18:57:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/08\/circuit-breaker-bulkhead-fallback\/"},"modified":"2026-10-08T18:57:00","modified_gmt":"2026-10-08T18:57:00","slug":"circuit-breaker-bulkhead-fallback","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/08\/circuit-breaker-bulkhead-fallback\/","title":{"rendered":"Circuit Breaker Neden Var? Yava\u015f Bir Ba\u011f\u0131ml\u0131l\u0131k T\u00fcm Sistemi D\u00fc\u015f\u00fcrebilir"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Da\u011f\u0131t\u0131k sistemlerde ilgin\u00e7 bir ger\u00e7ek var.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tamamen \u00e7\u00f6ken bir servis, yava\u015f \u00e7al\u0131\u015fan bir servisten daha az zarar verir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7\u00f6ken servise yap\u0131lan \u00e7a\u011fr\u0131 h\u0131zl\u0131ca hata al\u0131r. \u00c7a\u011f\u0131ran taraf bunu yakalar ve devam eder.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yava\u015f servise yap\u0131lan \u00e7a\u011fr\u0131 ise bekler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thread bekler. Connection bekler. Request bekler.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cascading failure<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir \u00f6neri servisinin yan\u0131t s\u00fcresinin 50 ms&#8217;den 10 saniyeye \u00e7\u0131kt\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcn.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00dcr\u00fcn sayfas\u0131 her istekte bu servisi \u00e7a\u011f\u0131r\u0131yor. \u00dcr\u00fcn servisinin 200 thread&#8217;i var.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Saniyede 50 istek geliyorsa, birka\u00e7 saniye i\u00e7inde 200 thread&#8217;in tamam\u0131 \u00f6neri servisinden cevap beklemeye ba\u015flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Art\u0131k \u00fcr\u00fcn servisi yeni istekleri kabul edemez. Sepet, \u00f6deme, arama gibi \u00f6neri servisiyle hi\u00e7bir ilgisi olmayan endpoint&#8217;ler de cevap veremez hale gelir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00dcr\u00fcn servisini \u00e7a\u011f\u0131ran gateway de ayn\u0131 \u015fekilde t\u0131kan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sistemin en \u00f6nemsiz par\u00e7as\u0131, en \u00f6nemli par\u00e7alar\u0131n\u0131 a\u015fa\u011f\u0131 \u00e7eker.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00d6nce timeout<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Circuit breaker&#8217;dan \u00f6nce konu\u015fulmas\u0131 gereken \u015fey timeout&#8217;tur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Timeout tan\u0131mlanmam\u0131\u015f bir HTTP client \u00e7a\u011fr\u0131s\u0131, da\u011f\u0131t\u0131k sistemdeki en tehlikeli sat\u0131rlardan biridir. Baz\u0131 client&#8217;lar\u0131n varsay\u0131lan timeout de\u011feri sonsuzdur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her d\u0131\u015f \u00e7a\u011fr\u0131n\u0131n bir \u00fcst s\u00fcre s\u0131n\u0131r\u0131 olmal\u0131. Bu s\u0131n\u0131r da tahmin edilerek de\u011fil, ger\u00e7ek latency da\u011f\u0131l\u0131m\u0131na bak\u0131larak belirlenmeli. Normalde p99&#8217;u 120 ms olan bir servis i\u00e7in 10 saniyelik timeout koruma sa\u011flamaz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Circuit breaker<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Timeout tek bir \u00e7a\u011fr\u0131y\u0131 korur. Circuit breaker ise bir ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n genel durumunu takip eder.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00dc\u00e7 durumu vard\u0131r:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Closed:<\/strong> \u00c7a\u011fr\u0131lar normal \u015fekilde ge\u00e7er. Hata oran\u0131 izlenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Open:<\/strong> Hata veya yava\u015f \u00e7a\u011fr\u0131 oran\u0131 e\u015fi\u011fi ge\u00e7mi\u015ftir. \u00c7a\u011fr\u0131lar ba\u011f\u0131ml\u0131l\u0131\u011fa hi\u00e7 g\u00f6nderilmeden an\u0131nda reddedilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Half-open:<\/strong> Bekleme s\u00fcresi dolduktan sonra s\u0131n\u0131rl\u0131 say\u0131da deneme \u00e7a\u011fr\u0131s\u0131 ge\u00e7irilir. Ba\u015far\u0131l\u0131 olurlarsa devre kapan\u0131r, olmazlarsa tekrar a\u00e7\u0131l\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Resilience4j ile tipik bir konfig\u00fcrasyon:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>resilience4j.circuitbreaker.instances.recommendation:\n  slidingWindowSize: 50\n  failureRateThreshold: 50\n  slowCallDurationThreshold: 500ms\n  slowCallRateThreshold: 50\n  waitDurationInOpenState: 30s<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Buradaki <code>slowCallRateThreshold<\/code> de\u011feri genellikle g\u00f6zden ka\u00e7ar. Breaker sadece hatalara de\u011fil, yava\u015f cevaplara da tepki verebilmelidir. Yukar\u0131daki senaryoda servis hata vermiyor, sadece yava\u015f.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Devre a\u00e7\u0131k oldu\u011funda iki \u015fey kazan\u0131l\u0131r. \u00c7a\u011f\u0131ran taraf thread&#8217;lerini korur. Zorlanan servis de \u00fczerine gelen y\u00fckten kurtulur ve toparlanma f\u0131rsat\u0131 bulur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fallback<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Devre a\u00e7\u0131kken ne d\u00f6nece\u011fiz?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu teknik bir karar de\u011fil, \u00fcr\u00fcn karar\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6neri servisi i\u00e7in bo\u015f bir liste veya \u00f6nceden cache&#8217;lenmi\u015f pop\u00fcler \u00fcr\u00fcnler d\u00f6nmek gayet kabul edilebilir. Kullan\u0131c\u0131 muhtemelen fark\u0131 bile g\u00f6rmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6deme servisi i\u00e7in ise sahte bir ba\u015far\u0131l\u0131 cevap d\u00f6nmek kabul edilemez. Burada a\u00e7\u0131k bir hata g\u00f6stermek do\u011fru davran\u0131\u015ft\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her ba\u011f\u0131ml\u0131l\u0131k i\u00e7in \u015fu soru sorulmal\u0131: bu servis yokken uygulama hangi deneyimi sunabilir?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bulkhead<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Gemilerde g\u00f6vde b\u00f6lmelere ayr\u0131l\u0131r. Bir b\u00f6lme su al\u0131rsa di\u011ferleri etkilenmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yaz\u0131l\u0131mda ayn\u0131 fikir kaynaklar\u0131 ba\u011f\u0131ml\u0131l\u0131klara g\u00f6re ay\u0131rmakt\u0131r. \u00d6neri servisi \u00e7a\u011fr\u0131lar\u0131 i\u00e7in ayr\u0131 ve s\u0131n\u0131rl\u0131 bir thread pool veya e\u015fzamanl\u0131 \u00e7a\u011fr\u0131 limiti tan\u0131mlan\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>recommendation: max 20 concurrent calls\npayment:        max 50 concurrent calls<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6neri servisi kilitlense bile en fazla 20 kayna\u011f\u0131 t\u00fcketebilir. \u00d6deme ak\u0131\u015f\u0131 \u00e7al\u0131\u015fmaya devam eder.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Circuit breaker&#8217;\u0131n devreye girmesi i\u00e7in bir s\u00fcre hata biriktirmesi gerekir. Bulkhead ise o s\u00fcre i\u00e7inde verilecek zarar\u0131 s\u0131n\u0131rlar. \u0130kisi birlikte kullan\u0131ld\u0131\u011f\u0131nda anlaml\u0131d\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Retry ile birlikte dikkat<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Retry, circuit breaker ve timeout&#8217;un birbirine g\u00f6re konumu \u00f6nemlidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Retry breaker&#8217;\u0131n d\u0131\u015f\u0131nda olursa, a\u00e7\u0131k devreye kar\u015f\u0131 bo\u015funa tekrar denemeler yap\u0131l\u0131r. Toplam timeout da retry say\u0131s\u0131yla birlikte d\u00fc\u015f\u00fcn\u00fclmelidir. \u00dc\u00e7 deneme ve 2 saniyelik timeout, kullan\u0131c\u0131n\u0131n 6 saniye beklemesi demektir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dayan\u0131kl\u0131l\u0131k k\u00fct\u00fcphaneleri bu ara\u00e7lar\u0131 haz\u0131r sunuyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama hangi ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n kritik oldu\u011funu, hangisinin olmadan ya\u015fanabilece\u011fini k\u00fct\u00fcphane bilemez. Bu karar\u0131 sistemin sahibi vermeli.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hata veren bir servis can s\u0131k\u0131c\u0131d\u0131r, yava\u015f cevap veren bir servis ise tehlikelidir. Circuit breaker, bulkhead ve fallback ile cascading failure nas\u0131l \u00f6nlenir?<\/p>\n","protected":false},"author":1,"featured_media":46,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-47","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dagitik-sistemler"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/47","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=47"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/47\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/46"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=47"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=47"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}