{"id":35,"date":"2026-09-26T18:14:00","date_gmt":"2026-09-26T18:14:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/26\/transactional-outbox-pattern\/"},"modified":"2026-09-26T18:14:00","modified_gmt":"2026-09-26T18:14:00","slug":"transactional-outbox-pattern","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/26\/transactional-outbox-pattern\/","title":{"rendered":"Veritaban\u0131na Yazd\u0131m, Event&#8217;i G\u00f6nderemedim: Transactional Outbox"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">\u015eu kod ilk bak\u0131\u015fta masum g\u00f6r\u00fcn\u00fcr:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>orderRepository.save(order);\neventPublisher.publish(new OrderCreated(order.getId()));<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nce sipari\u015fi kaydediyoruz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sonra di\u011fer servislere haber veriyoruz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Peki <code>save<\/code> ba\u015far\u0131l\u0131 olduktan sonra uygulama <code>publish<\/code> \u00e7a\u011fr\u0131s\u0131ndan \u00f6nce kapan\u0131rsa ne olur?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sipari\u015f veritaban\u0131nda vard\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama stok servisi, fatura servisi ve bildirim servisi bu sipari\u015ften hi\u00e7 haberdar olmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">S\u0131ray\u0131 ters \u00e7evirmek de \u00e7\u00f6z\u00fcm de\u011fildir. Bu sefer event gider ama transaction rollback olabilir. Di\u011fer servisler var olmayan bir sipari\u015f i\u00e7in i\u015f yapmaya ba\u015flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu probleme <strong>dual write<\/strong> deniyor. \u0130ki farkl\u0131 sisteme yaz\u0131yoruz ve ikisini ayn\u0131 atomik i\u015flem i\u00e7inde tutam\u0131yoruz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Neden distributed transaction kullanm\u0131yoruz?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Teoride XA veya two-phase commit ile veritaban\u0131 ve broker ayn\u0131 transaction&#8217;a sokulabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pratikte \u00e7o\u011fu modern broker bunu desteklemiyor. Destekleyenlerde de coordinator&#8217;\u0131n kendisi yeni bir ar\u0131za noktas\u0131 haline geliyor. Lock s\u00fcreleri uzuyor, throughput d\u00fc\u015f\u00fcyor, operasyon zorla\u015f\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden \u00e7o\u011fu sistem ba\u015fka bir yol se\u00e7er: atomikli\u011fi tek bir yere, yani veritaban\u0131na b\u0131rakmak.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Outbox tablosu<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Fikir basit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Event&#8217;i do\u011frudan broker&#8217;a g\u00f6ndermek yerine ayn\u0131 transaction i\u00e7inde bir tabloya yazar\u0131z:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>BEGIN;\n\nINSERT INTO orders (id, customer_id, total)\nVALUES (...);\n\nINSERT INTO outbox (id, aggregate_id, type, payload, created_at)\nVALUES (...);\n\nCOMMIT;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ya ikisi birden yaz\u0131l\u0131r ya da hi\u00e7biri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Art\u0131k &#8220;sipari\u015f var ama event yok&#8221; durumu m\u00fcmk\u00fcn de\u011fildir. Event hen\u00fcz g\u00f6nderilmemi\u015f olabilir ama kaybolmam\u0131\u015ft\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Relay<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Outbox tablosundaki kay\u0131tlar\u0131 broker&#8217;a ta\u015f\u0131yan ayr\u0131 bir s\u00fcre\u00e7 gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ki yayg\u0131n yakla\u015f\u0131m var.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Birincisi polling:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SELECT * FROM outbox\nWHERE published_at IS NULL\nORDER BY created_at\nLIMIT 100\nFOR UPDATE SKIP LOCKED;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Basit, anla\u015f\u0131l\u0131r, \u00e7o\u011fu proje i\u00e7in yeterli. <code>SKIP LOCKED<\/code> sayesinde birden fazla relay instance&#8217;\u0131 ayn\u0131 sat\u0131rlar\u0131 kap\u0131\u015fmadan \u00e7al\u0131\u015fabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130kincisi change data capture. Debezium gibi bir ara\u00e7 veritaban\u0131n\u0131n transaction log&#8217;unu okur ve outbox&#8217;a eklenen sat\u0131rlar\u0131 event&#8217;e d\u00f6n\u00fc\u015ft\u00fcr\u00fcr. Polling y\u00fck\u00fc yoktur, gecikme d\u00fc\u015f\u00fckt\u00fcr. Ama operasyonel olarak daha a\u011f\u0131r bir par\u00e7ad\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ben genellikle polling ile ba\u015flamay\u0131 \u00f6neriyorum. Gecikme veya veritaban\u0131 y\u00fck\u00fc ger\u00e7ekten problem oldu\u011funda CDC&#8217;ye ge\u00e7mek zor de\u011fil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">At-least-once ka\u00e7\u0131n\u0131lmazd\u0131r<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Relay mesaj\u0131 broker&#8217;a g\u00f6nderdi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>published_at<\/code> alan\u0131n\u0131 g\u00fcncellemeden \u00f6nce kapand\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yeniden ba\u015flad\u0131\u011f\u0131nda ayn\u0131 mesaj\u0131 tekrar g\u00f6nderecek.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Outbox pattern exactly-once delivery sa\u011flamaz. At-least-once sa\u011flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden t\u00fcketici taraf\u0131 idempotent olmal\u0131d\u0131r. En pratik y\u00f6ntem event ID&#8217;yi bir <code>processed_events<\/code> tablosunda tutmak:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>INSERT INTO processed_events (event_id)\nVALUES (:id)\nON CONFLICT DO NOTHING;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Sat\u0131r eklenmediyse event daha \u00f6nce i\u015flenmi\u015ftir. T\u00fcketici i\u015fi atlar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burada \u00f6nemli olan, bu kontrol\u00fcn de t\u00fcketicinin kendi i\u015f transaction&#8217;\u0131 i\u00e7inde yap\u0131lmas\u0131d\u0131r. Aksi halde ayn\u0131 problemi bu sefer kar\u015f\u0131 tarafta ya\u015far\u0131z.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u0131ralama<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Outbox kay\u0131tlar\u0131 <code>created_at<\/code> ile okunur ama birden fazla relay varsa s\u0131ralama garantisi zay\u0131flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7o\u011fu durumda global s\u0131ralamaya ihtiya\u00e7 yoktur. \u00d6nemli olan ayn\u0131 aggregate&#8217;e ait event&#8217;lerin s\u0131ras\u0131d\u0131r. <code>OrderCreated<\/code> event&#8217;inin <code>OrderCancelled<\/code> event&#8217;inden sonra i\u015flenmesi ger\u00e7ek bir problemdir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kafka kullan\u0131yorsan\u0131z mesaj key&#8217;i olarak <code>aggregate_id<\/code> vermek bu s\u0131ray\u0131 partition seviyesinde korur. Relay taraf\u0131nda da ayn\u0131 aggregate&#8217;e ait kay\u0131tlar\u0131n tek bir worker taraf\u0131ndan i\u015flenmesi gerekir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Tablo b\u00fcy\u00fcr<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unutulan bir detay: outbox tablosu s\u00fcrekli b\u00fcy\u00fcr.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00f6nderilmi\u015f kay\u0131tlar\u0131 belirli bir s\u00fcre sonra silen veya ar\u015fivleyen bir job gerekir. Aksi halde birka\u00e7 ay sonra relay sorgusunun yava\u015flad\u0131\u011f\u0131n\u0131 fark edersiniz. <code>published_at IS NULL<\/code> ko\u015fuluna uygun bir partial index de i\u015fleri ciddi \u015fekilde h\u0131zland\u0131r\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Outbox pattern parlak bir teknoloji de\u011fil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir tablo, bir sorgu ve biraz disiplin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama &#8220;veritaban\u0131na yazd\u0131m, event&#8217;i g\u00f6nderemedim&#8221; c\u00fcmlesini production loglar\u0131nda g\u00f6rmemenin en sade yolu bu.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sipari\u015f kaydedildi ama event broker&#8217;a hi\u00e7 ula\u015fmad\u0131. Dual write problemini transactional outbox ile nas\u0131l \u00e7\u00f6zeriz, relay taraf\u0131nda nelere dikkat etmek gerekir?<\/p>\n","protected":false},"author":1,"featured_media":34,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-35","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\/35","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=35"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/35\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/34"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=35"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=35"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=35"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}