{"id":247,"date":"2026-11-17T07:50:00","date_gmt":"2026-11-17T07:50:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/?p=247"},"modified":"2026-11-17T07:50:00","modified_gmt":"2026-11-17T07:50:00","slug":"mikroservis-iletisimi-senkron-asenkron","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/17\/mikroservis-iletisimi-senkron-asenkron\/","title":{"rendered":"Mikroservisler Aras\u0131 \u0130leti\u015fim: Senkron mu Asenkron mu?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Mikroservisler aras\u0131 ileti\u015fim<\/strong>, bir servisin ba\u015fka bir servisten veri istemesi veya ona bir \u015fey oldu\u011funu bildirmesi i\u00e7in kulland\u0131\u011f\u0131 y\u00f6ntemdir. Temelde iki model var: \u00e7a\u011f\u0131ran\u0131n cevab\u0131 bekledi\u011fi senkron ileti\u015fim (REST, gRPC) ve mesaj\u0131n bir arac\u0131ya b\u0131rak\u0131l\u0131p cevab\u0131n beklenmedi\u011fi asenkron ileti\u015fim (Kafka, RabbitMQ gibi mesaj sistemleri). Hangisinin se\u00e7ildi\u011fi, sistemin hata an\u0131nda nas\u0131l davranaca\u011f\u0131n\u0131 belirleyen en \u00f6nemli mimari kararlardan biri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yaz\u0131da iki modeli ba\u011f\u0131ml\u0131l\u0131k, tutarl\u0131l\u0131k ve hata davran\u0131\u015f\u0131 a\u00e7\u0131s\u0131ndan kar\u015f\u0131la\u015ft\u0131raca\u011f\u0131m ve hangi durumda hangisini tercih etti\u011fimi anlataca\u011f\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Senkron ileti\u015fim nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sipari\u015f servisi, stok servisine bir HTTP iste\u011fi g\u00f6nderir ve cevab\u0131 bekler:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>POST \/stock\/reservations\n{ \"productId\": 42, \"quantity\": 1 }\n\n\u2190 201 Created<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Cevap gelene kadar sipari\u015f servisi i\u015flemi tamamlayamaz. Cevap olumluysa devam eder, olumsuzsa kullan\u0131c\u0131ya hata g\u00f6sterir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu modelin en b\u00fcy\u00fck avantaj\u0131 basitli\u011fidir. Ak\u0131\u015f kodda yukar\u0131dan a\u015fa\u011f\u0131ya okunur. Hata an\u0131nda \u00e7a\u011f\u0131rana hemen bilgi verilir. Debug etmek kolayd\u0131r, bir iste\u011fin yolu tek bir trace \u00fczerinde g\u00f6r\u00fcl\u00fcr.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Senkron ileti\u015fimin bedeli nedir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bedeli ise zamansal ba\u011f\u0131ml\u0131l\u0131kt\u0131r. Sipari\u015f servisi, stok servisi ayakta olmadan \u00e7al\u0131\u015famaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ba\u011f\u0131ml\u0131l\u0131k zincirleme \u015fekilde b\u00fcy\u00fcr. Sipari\u015f servisi stok servisini, stok servisi depo servisini, depo servisi kargo servisini \u00e7a\u011f\u0131r\u0131yorsa, kullan\u0131c\u0131n\u0131n sipari\u015f verebilmesi i\u00e7in d\u00f6rt servisin ayn\u0131 anda sa\u011fl\u0131kl\u0131 olmas\u0131 gerekir. Her birinin eri\u015filebilirli\u011fi y\u00fczde 99,9 ise, zincirin toplam eri\u015filebilirli\u011fi yakla\u015f\u0131k y\u00fczde 99,6&#8217;ya d\u00fc\u015fer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Gecikme de toplan\u0131r. Her \u00e7a\u011fr\u0131n\u0131n s\u00fcresi, kullan\u0131c\u0131n\u0131n bekleme s\u00fcresine eklenir. Zincirdeki en yava\u015f servis, b\u00fct\u00fcn ak\u0131\u015f\u0131n h\u0131z\u0131n\u0131 belirler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">En tehlikeli durum ise bir servisin tamamen \u00e7\u00f6kmesi de\u011fil, yava\u015flamas\u0131d\u0131r. Yava\u015f bir ba\u011f\u0131ml\u0131l\u0131k, \u00e7a\u011f\u0131ran servisin thread&#8217;lerini ve connection&#8217;lar\u0131n\u0131 me\u015fgul eder ve hata zincirleme \u015fekilde yay\u0131l\u0131r. Bu durumu ve \u00f6nlemlerini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/08\/circuit-breaker-bulkhead-fallback\/\">circuit breaker ve bulkhead<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m. Retry ve timeout&#8217;lar\u0131n do\u011fru kurulmas\u0131 da ayn\u0131 \u00f6l\u00e7\u00fcde \u00f6nemli. Onu da <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/23\/retry-timeout-backoff-jitter-distributed-systems\/\">retry, backoff ve jitter<\/a> yaz\u0131s\u0131nda ele ald\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Asenkron ileti\u015fim nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Asenkron modelde sipari\u015f servisi bir event yay\u0131nlar ve i\u015fine devam eder:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>OrderPlaced { orderId: 9182, items: [...] }<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Event bir mesaj sistemine b\u0131rak\u0131l\u0131r. Stok servisi, fatura servisi ve bildirim servisi bu event&#8217;i kendi h\u0131zlar\u0131nda okur ve i\u015fler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sipari\u015f servisi stok servisinin ayakta olup olmad\u0131\u011f\u0131n\u0131 bilmez ve bilmesi gerekmez. Stok servisi bir saatli\u011fine kapal\u0131 olsa bile sipari\u015fler al\u0131nmaya devam eder. Stok servisi geri geldi\u011finde, kuyrukta biriken event&#8217;leri i\u015fler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu, zamansal ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n ortadan kalkmas\u0131 demek. Servisler birbirinden ba\u011f\u0131ms\u0131z olarak deploy edilebilir, \u00f6l\u00e7eklenebilir ve ar\u0131zalanabilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Asenkron ileti\u015fimin bedeli nedir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Asenkronluk \u00fccretsiz de\u011fil. Getirdi\u011fi karma\u015f\u0131kl\u0131k genellikle hafife al\u0131n\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Eventual consistency.<\/strong> Sipari\u015f olu\u015fturuldu\u011fu anda stok hen\u00fcz ayr\u0131lmam\u0131\u015ft\u0131r. Sistem bir s\u00fcre tutars\u0131z bir ara durumdad\u0131r. Kullan\u0131c\u0131 aray\u00fcz\u00fc ve i\u015f kurallar\u0131 bu ara durumu hesaba katmal\u0131d\u0131r. Bu konuyu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/17\/cqrs-read-model-eventual-consistency\/\">CQRS ve eventual consistency<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Hata y\u00f6netimi.<\/strong> Stok yetersizse ne olacak? Senkron modelde kullan\u0131c\u0131ya hemen hata g\u00f6sterilir. Asenkron modelde sipari\u015f zaten kabul edilmi\u015ftir ve sonradan iptal edilmesi, \u00f6demenin iade edilmesi gerekir. Bu telafi mant\u0131\u011f\u0131n\u0131n tasar\u0131m\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/06\/saga-pattern-distributed-transactions\/\">saga pattern<\/a> yaz\u0131s\u0131n\u0131n konusuydu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teslimat garantileri.<\/strong> Mesajlar tekrar gelebilir, s\u0131ras\u0131 bozulabilir veya i\u015flenemeyip bir kenarda birikebilir. T\u00fcketicilerin idempotent olmas\u0131 ve i\u015flenemeyen mesajlar\u0131n y\u00f6netilmesi gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>G\u00f6r\u00fcn\u00fcrl\u00fck.<\/strong> Bir iste\u011fin yolu art\u0131k tek bir HTTP \u00e7a\u011fr\u0131 zincirinde de\u011fil, kuyruklar \u00fczerinden da\u011f\u0131lm\u0131\u015f asenkron ad\u0131mlarda. Trace context&#8217;in mesajlarla ta\u015f\u0131nmad\u0131\u011f\u0131 bir sistemde, bir sipari\u015fin nerede tak\u0131ld\u0131\u011f\u0131n\u0131 bulmak zorla\u015f\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Atomik yay\u0131n.<\/strong> Veritaban\u0131na yaz\u0131p sonra event yay\u0131nlamak, iki ayr\u0131 sisteme yazmak demek. Aradaki bir \u00e7\u00f6kme event&#8217;in kaybolmas\u0131na yol a\u00e7ar. Bunun standart \u00e7\u00f6z\u00fcm\u00fc <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/26\/transactional-outbox-pattern\/\">transactional outbox<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kar\u015f\u0131la\u015ft\u0131rma tablosu<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Kriter<\/th><th>Senkron (REST, gRPC)<\/th><th>Asenkron (mesajla\u015fma)<\/th><\/tr><\/thead><tbody><tr><td>Zamansal ba\u011f\u0131ml\u0131l\u0131k<\/td><td>Y\u00fcksek, kar\u015f\u0131 taraf ayakta olmal\u0131<\/td><td>D\u00fc\u015f\u00fck, kar\u015f\u0131 taraf sonra i\u015fleyebilir<\/td><\/tr><tr><td>Cevap<\/td><td>Hemen, kesin<\/td><td>Yok veya sonradan<\/td><\/tr><tr><td>Tutarl\u0131l\u0131k<\/td><td>\u0130\u015flem an\u0131nda net<\/td><td>Eventual consistency<\/td><\/tr><tr><td>Gecikme<\/td><td>Zincir boyunca toplan\u0131r<\/td><td>\u00c7a\u011f\u0131ran i\u00e7in d\u00fc\u015f\u00fck<\/td><\/tr><tr><td>Hata y\u00f6netimi<\/td><td>Basit, hata \u00e7a\u011f\u0131rana d\u00f6ner<\/td><td>Telafi, DLQ, retry<\/td><\/tr><tr><td>Debug<\/td><td>Kolay<\/td><td>Trace context gerektirir<\/td><\/tr><tr><td>Y\u00fck dalgalanmas\u0131<\/td><td>Hedef servise do\u011frudan yans\u0131r<\/td><td>Kuyruk tampon g\u00f6revi g\u00f6r\u00fcr<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Komut mu, event mi?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Asenkron ileti\u015fimde de iki farkl\u0131 niyet var ve bunlar\u0131 kar\u0131\u015ft\u0131rmamak gerekiyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Komut<\/strong>, bir servisin ba\u015fka bir servisten bir i\u015f yapmas\u0131n\u0131 istemesidir. <code>ReserveStock<\/code>, <code>SendInvoiceEmail<\/code>. G\u00f6nderen, i\u015fin yap\u0131lmas\u0131n\u0131 bekler ve genellikle tek bir al\u0131c\u0131s\u0131 vard\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Event<\/strong>, ge\u00e7mi\u015fte olmu\u015f bir \u015feyin duyurusudur. <code>OrderPlaced<\/code>, <code>PaymentCompleted<\/code>. Yay\u0131nlayan, kimin dinledi\u011fini bilmez ve \u00f6nemsemez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Event&#8217;ler servisler aras\u0131ndaki ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 daha fazla azalt\u0131r, \u00e7\u00fcnk\u00fc yay\u0131nlayan taraf t\u00fcketicileri tan\u0131maz. Ama i\u015f ak\u0131\u015f\u0131 tek bir yerde yaz\u0131l\u0131 olmad\u0131\u011f\u0131 i\u00e7in b\u00fcy\u00fck sistemlerde takip etmesi zorla\u015f\u0131r. Kuyruk ile event log aras\u0131ndaki fark\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/23\/kafka-rabbitmq-queue-event-log\/\">Kafka ve RabbitMQ<\/a> yaz\u0131s\u0131nda, i\u00e7 event&#8217;lerle d\u0131\u015far\u0131ya yay\u0131nlanan event&#8217;lerin fark\u0131n\u0131 da <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/08\/domain-events-vs-integration-events\/\">domain ve integration event<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hangi durumda hangisini se\u00e7iyorum?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Benim kulland\u0131\u011f\u0131m pratik kurallar \u015funlar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Kullan\u0131c\u0131 cevab\u0131 bekliyorsa ve cevap ba\u015fka bir servise ba\u011fl\u0131ysa, senkron.<\/strong> Kullan\u0131c\u0131 \u00fcr\u00fcn sayfas\u0131n\u0131 a\u00e7t\u0131\u011f\u0131nda fiyat bilgisi gerekiyorsa, fiyat servisini \u00e7a\u011f\u0131rmak gerekir. Bu bilgiyi bir event ile almak anlams\u0131zd\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bir i\u015fin sonucu sonradan gelebiliyorsa, asenkron.<\/strong> Sipari\u015f sonras\u0131 e-posta, fatura olu\u015fturma, raporlama, arama index&#8217;ini g\u00fcncelleme. Kullan\u0131c\u0131 bu i\u015flerin tamamlanmas\u0131n\u0131 beklemez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bir olay birden fazla servisi ilgilendiriyorsa, event.<\/strong> Sipari\u015f olu\u015fturuldu\u011funda be\u015f farkl\u0131 servisin bilgilendirilmesi gerekiyorsa, sipari\u015f servisinin bu be\u015f servisi tek tek \u00e7a\u011f\u0131rmas\u0131 onu hepsine ba\u011f\u0131ml\u0131 yapar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Karar i\u00e7in ba\u015fka bir servisin verisine s\u00fcrekli ihtiya\u00e7 varsa, verinin kopyas\u0131n\u0131 tutmay\u0131 d\u00fc\u015f\u00fcn.<\/strong> Sipari\u015f servisi her sipari\u015fte m\u00fc\u015fteri servisine &#8220;bu m\u00fc\u015fteri aktif mi?&#8221; diye soruyorsa, m\u00fc\u015fteri durumundaki de\u011fi\u015fiklikleri event olarak dinleyip yerel bir kopya tutmak, senkron ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 ortadan kald\u0131r\u0131r. Bedeli, kopyan\u0131n k\u0131sa bir s\u00fcre eski olabilmesi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Mesaj kuyru\u011fu \u00fczerinden istek-cevap kullan\u0131lmal\u0131 m\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Baz\u0131 ekipler senkron ba\u011f\u0131ml\u0131l\u0131ktan ka\u00e7\u0131nmak i\u00e7in istek-cevap kal\u0131b\u0131n\u0131 mesaj kuyru\u011fu \u00fczerinden kurar. Sipari\u015f servisi bir kuyru\u011fa <code>CheckStock<\/code> mesaj\u0131 b\u0131rak\u0131r, cevab\u0131 ba\u015fka bir kuyrukta bekler ve bir correlation ID ile e\u015fle\u015ftirir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu kal\u0131p teknik olarak \u00e7al\u0131\u015f\u0131r ama \u00e7o\u011fu zaman iki d\u00fcnyan\u0131n k\u00f6t\u00fc yanlar\u0131n\u0131 birle\u015ftirir. \u00c7a\u011f\u0131ran taraf yine cevab\u0131 beklemek zorundad\u0131r, yani zamansal ba\u011f\u0131ml\u0131l\u0131k ortadan kalkmam\u0131\u015ft\u0131r. \u00dcst\u00fcne mesaj sisteminin getirdi\u011fi gecikme, ek altyap\u0131 ve daha zor debug eklenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130stek-cevab\u0131n mesajla\u015fma \u00fczerinden mant\u0131kl\u0131 oldu\u011fu durumlar da var. Cevab\u0131n dakikalar veya saatler i\u00e7inde gelebildi\u011fi uzun s\u00fcren i\u015fler, \u00e7a\u011f\u0131ran\u0131n cevap gelene kadar ba\u015fka i\u015fler yapabildi\u011fi ak\u0131\u015flar ve y\u00fck dalgalanmas\u0131n\u0131n tampona al\u0131nmas\u0131 gereken durumlar. Kullan\u0131c\u0131n\u0131n saniyeler i\u00e7inde cevap bekledi\u011fi bir ak\u0131\u015fta ise do\u011frudan senkron \u00e7a\u011fr\u0131 genellikle daha d\u00fcr\u00fcst bir tasar\u0131md\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Senkron ileti\u015fimde hangi protokol?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Senkron modeli se\u00e7tikten sonra da bir karar daha var: REST mi, gRPC mi?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">REST, HTTP ve JSON \u00fczerine kurulu oldu\u011fu i\u00e7in her yerde \u00e7al\u0131\u015f\u0131r, taray\u0131c\u0131dan test edilebilir ve \u00f6\u011frenmesi kolayd\u0131r. gRPC ise ikili format\u0131, HTTP\/2 \u00fczerinden \u00e7oklu ak\u0131\u015f\u0131 ve s\u00f6zle\u015fmeden \u00fcretilen tipli client&#8217;lar\u0131yla servisler aras\u0131 i\u00e7 trafikte performans ve tip g\u00fcvenli\u011fi sa\u011flar. Ben d\u0131\u015far\u0131ya a\u00e7\u0131k API&#8217;lerde REST, y\u00fcksek hacimli i\u00e7 servis trafi\u011finde gRPC&#8217;yi de\u011ferlendiriyorum. Ama bu, ileti\u015fim modeli karar\u0131ndan sonra gelen ikincil bir karar. Senkron mu asenkron mu sorusunun cevab\u0131n\u0131 de\u011fi\u015ftirmiyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Senkron \u00e7a\u011fr\u0131 zincirleri bir uyar\u0131 i\u015faretidir<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir kullan\u0131c\u0131 iste\u011finin arka planda d\u00f6rt be\u015f servisi s\u0131rayla \u00e7a\u011f\u0131rd\u0131\u011f\u0131 bir yap\u0131 g\u00f6r\u00fcyorsam, bunu genellikle servis s\u0131n\u0131rlar\u0131n\u0131n yanl\u0131\u015f \u00e7izildi\u011fine dair bir i\u015faret olarak okuyorum.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131k birlikte de\u011fi\u015fen ve s\u00fcrekli birbirini \u00e7a\u011f\u0131ran iki servis, asl\u0131nda tek bir sorumlulu\u011fun iki par\u00e7as\u0131 olabilir. Bu durumda ileti\u015fim modelini de\u011fi\u015ftirmek yerine s\u0131n\u0131r\u0131 yeniden d\u00fc\u015f\u00fcnmek daha do\u011fru bir \u00e7\u00f6z\u00fcm olabilir. Servis s\u0131n\u0131rlar\u0131n\u0131n nas\u0131l belirlendi\u011fini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/23\/ddd-bounded-context-modular-architecture\/\">DDD ve bounded context<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ayr\u0131ca bir\u00e7ok sistem i\u00e7in bu karma\u015f\u0131kl\u0131\u011f\u0131n hi\u00e7 gerekmeyebilece\u011fini de hat\u0131rlatmak isterim. Ayn\u0131 s\u00fcre\u00e7 i\u00e7inde \u00e7al\u0131\u015fan mod\u00fcller aras\u0131nda ileti\u015fim, a\u011f hatas\u0131, timeout ve serialization problemleri olmadan yap\u0131l\u0131r. Bu yakla\u015f\u0131m\u0131n ne zaman daha do\u011fru oldu\u011funu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/23\/mikroservis-mi-moduler-monolit-mi\/\">mod\u00fcler monolit<\/a> yaz\u0131s\u0131nda tart\u0131\u015fm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hibrit yakla\u015f\u0131m<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ger\u00e7ek sistemlerin \u00e7o\u011fu iki modeli birlikte kullan\u0131r. Benim s\u0131k kulland\u0131\u011f\u0131m bir kal\u0131p \u015fu:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Kullan\u0131c\u0131 iste\u011fi senkron olarak, m\u00fcmk\u00fcn oldu\u011funca az servis \u00fczerinden i\u015flenir.<\/li>\n\n\n<li>\u0130\u015flemin kendi veritaban\u0131na yaz\u0131lmas\u0131 ve outbox ile event yay\u0131nlanmas\u0131 ayn\u0131 transaction&#8217;da yap\u0131l\u0131r.<\/li>\n\n\n<li>Di\u011fer servisler event&#8217;leri asenkron olarak i\u015fler.<\/li>\n\n\n<li>Kullan\u0131c\u0131n\u0131n bu asenkron sonu\u00e7lar\u0131 g\u00f6rmesi gerekiyorsa, durum sorgulanabilir bir kaynak olarak sunulur.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yap\u0131da kullan\u0131c\u0131 kritik yolda sadece ger\u00e7ekten gerekli ba\u011f\u0131ml\u0131l\u0131klar\u0131 bekler. Geri kalan her \u015fey, sistemin dayan\u0131kl\u0131l\u0131\u011f\u0131n\u0131 etkilemeden arka planda ger\u00e7ekle\u015fir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Martin Fowler ve James Lewis&#8217;in <a href=\"https:\/\/martinfowler.com\/articles\/microservices.html\" target=\"_blank\" rel=\"noopener\">mikroservisler \u00fczerine makalesi<\/a>, &#8220;smart endpoints and dumb pipes&#8221; ilkesiyle bu ileti\u015fim kararlar\u0131n\u0131n arkas\u0131ndaki d\u00fc\u015f\u00fcnceyi iyi \u00f6zetliyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130leti\u015fim modeli se\u00e7imi, bir teknoloji se\u00e7imi gibi g\u00f6r\u00fcnse de asl\u0131nda bir hata davran\u0131\u015f\u0131 se\u00e7imi. As\u0131l soru &#8220;hangisi daha modern?&#8221; de\u011fil, &#8220;bu servis ayakta de\u011filken kullan\u0131c\u0131 ne ya\u015famal\u0131?&#8221; sorusu.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Mikroservisler aras\u0131 ileti\u015fimde REST mi, mesaj kuyru\u011fu mu? Senkron ve asenkron modelleri ba\u011f\u0131ml\u0131l\u0131k, tutarl\u0131l\u0131k ve hata davran\u0131\u015f\u0131 a\u00e7\u0131s\u0131ndan kar\u015f\u0131la\u015ft\u0131r\u0131yoruz.<\/p>\n","protected":false},"author":1,"featured_media":246,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-247","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\/247","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=247"}],"version-history":[{"count":1,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/247\/revisions"}],"predecessor-version":[{"id":283,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/247\/revisions\/283"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/246"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}