{"id":63,"date":"2026-10-21T18:08:00","date_gmt":"2026-10-21T18:08:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/21\/multi-tenant-saas-data-isolation\/"},"modified":"2026-10-21T18:08:00","modified_gmt":"2026-10-21T18:08:00","slug":"multi-tenant-saas-data-isolation","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/21\/multi-tenant-saas-data-isolation\/","title":{"rendered":"Multi-Tenant SaaS&#8217;ta Veri \u0130zolasyonu: Bir WHERE Ko\u015fulunu Unutmak"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir SaaS \u00fcr\u00fcn\u00fcnde ya\u015fanabilecek en k\u00f6t\u00fc olaylardan biri performans problemi de\u011fildir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir m\u00fc\u015fterinin, ba\u015fka bir m\u00fc\u015fterinin verisini g\u00f6rmesidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu genellikle karma\u015f\u0131k bir sald\u0131r\u0131yla olmaz. Bir geli\u015ftiricinin yeni bir rapor sorgusu yazarken \u015fu sat\u0131r\u0131 unutmas\u0131yla olur:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>AND tenant_id = :tenantId<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">\u00dc\u00e7 model<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Multi-tenant veri izolasyonu i\u00e7in genellikle \u00fc\u00e7 yakla\u015f\u0131m konu\u015fulur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Payla\u015f\u0131lan tablolar.<\/strong> B\u00fct\u00fcn tenant&#8217;lar\u0131n verisi ayn\u0131 tablolarda durur. Her sat\u0131rda <code>tenant_id<\/code> vard\u0131r. En ucuz ve en kolay \u00f6l\u00e7eklenen modeldir. Yeni m\u00fc\u015fteri eklemek bir sat\u0131r insert etmektir. \u0130zolasyon tamamen uygulaman\u0131n do\u011frulu\u011funa ba\u011fl\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tenant ba\u015f\u0131na \u015fema.<\/strong> Ayn\u0131 veritaban\u0131nda her m\u00fc\u015fteri i\u00e7in ayr\u0131 bir \u015fema. \u0130zolasyon daha g\u00fc\u00e7l\u00fcd\u00fcr, yedekleme ve geri y\u00fckleme m\u00fc\u015fteri baz\u0131nda yap\u0131labilir. Ama y\u00fczlerce \u015femada migration \u00e7al\u0131\u015ft\u0131rmak ayr\u0131 bir operasyon problemidir. Binlerce \u015femaya \u00e7\u0131k\u0131ld\u0131\u011f\u0131nda veritaban\u0131 katalog boyutu da sorun olmaya ba\u015flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tenant ba\u015f\u0131na veritaban\u0131.<\/strong> En g\u00fc\u00e7l\u00fc izolasyon. B\u00fcy\u00fck m\u00fc\u015fteriler i\u00e7in veri konumu, \u015fifreleme anahtar\u0131 ve performans izolasyonu gibi gereksinimler kar\u015f\u0131lanabilir. En pahal\u0131 model.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pratikte \u00e7o\u011fu B2B SaaS payla\u015f\u0131lan tablolarla ba\u015fl\u0131yor. B\u00fcy\u00fck ve \u00f6zel gereksinimleri olan m\u00fc\u015fteriler i\u00e7in ayr\u0131 veritaban\u0131 se\u00e7ene\u011fi sonradan ekleniyor. \u0130ki modeli birlikte destekleyebilmek de mimarinin ba\u015ftan buna g\u00f6re kurulmas\u0131n\u0131 gerektiriyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Filtreyi geli\u015ftiriciye b\u0131rakmamak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Payla\u015f\u0131lan tablo modelinde as\u0131l soru \u015fu: tenant filtresinin her sorguda bulunmas\u0131n\u0131 nas\u0131l garanti ederiz?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Code review ile garanti edilemez. Y\u00fczlerce sorgu var ve bir tanesinin g\u00f6zden ka\u00e7mas\u0131 yeterli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Filtre, geli\u015ftiricinin hat\u0131rlamas\u0131na gerek kalmadan uygulanmal\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hibernate taraf\u0131nda <code>@TenantId<\/code> anotasyonu veya filter mekanizmas\u0131 bunu ORM seviyesinde sa\u011fl\u0131yor. Ama native sorgular, raporlama ara\u00e7lar\u0131 veya ba\u015fka bir servisin do\u011frudan veritaban\u0131na eri\u015fmesi bu katman\u0131 atlar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Row Level Security<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden ben izolasyonu m\u00fcmk\u00fcn oldu\u011funca veritaban\u0131na yak\u0131n kurmay\u0131 tercih ediyorum.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PostgreSQL&#8217;in Row Level Security \u00f6zelli\u011fi bunun i\u00e7in \u00e7ok uygun:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;\n\nCREATE POLICY tenant_isolation ON invoices\nUSING (tenant_id = current_setting('app.tenant_id')::uuid);<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulama her transaction ba\u015f\u0131nda tenant&#8217;\u0131 set eder:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SET LOCAL app.tenant_id = '6f1c...';<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Art\u0131k <code>WHERE<\/code> ko\u015fulu unutulsa bile veritaban\u0131 sadece o tenant&#8217;\u0131n sat\u0131rlar\u0131n\u0131 d\u00f6nd\u00fcr\u00fcr.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dikkat edilmesi gereken birka\u00e7 nokta var. Tablo sahibi olan rol RLS&#8217;den varsay\u0131lan olarak muaft\u0131r, bu y\u00fczden uygulama tablo sahibi olmayan ayr\u0131 bir rol ile ba\u011flanmal\u0131. Connection pool kullan\u0131l\u0131yorsa <code>SET<\/code> yerine <code>SET LOCAL<\/code> kullanmak gerekir, yoksa bir \u00f6nceki iste\u011fin tenant bilgisi connection \u00fczerinde kalabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu son madde \u00f6zellikle tehlikeli. Pool&#8217;a geri d\u00f6nen bir connection&#8217;da \u00f6nceki tenant&#8217;\u0131n ayar\u0131 kal\u0131rsa, sonraki istek yanl\u0131\u015f tenant&#8217;\u0131n verisini g\u00f6rebilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Tenant bilgisi nereden geliyor?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130zolasyonun ikinci yar\u0131s\u0131, tenant kimli\u011finin g\u00fcvenilir bir kaynaktan al\u0131nmas\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Request body&#8217;den veya query parametresinden gelen <code>tenantId<\/code> de\u011ferine g\u00fcvenmek yanl\u0131\u015f. Kullan\u0131c\u0131 bunu de\u011fi\u015ftirebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tenant bilgisi kimlik do\u011frulama s\u0131ras\u0131nda belirlenmeli, \u00f6rne\u011fin token i\u00e7indeki do\u011frulanm\u0131\u015f bir claim&#8217;den, ve request ba\u011flam\u0131na oradan aktar\u0131lmal\u0131. Asenkron i\u015flerde, kuyruklarda ve scheduled job&#8217;larda bu ba\u011flam\u0131n da ta\u015f\u0131nmas\u0131 gerekir. En \u00e7ok s\u0131z\u0131nt\u0131 arka plan i\u015flerinde ya\u015fan\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Di\u011fer payla\u015f\u0131lan kaynaklar<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Veritaban\u0131 izolasyonu tek ba\u015f\u0131na yetmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cache key&#8217;lerinde tenant yoksa, iki m\u00fc\u015fteri ayn\u0131 key&#8217;e denk gelen veriyi payla\u015fabilir. Dosya depolamada path&#8217;ler tenant baz\u0131nda ayr\u0131lmal\u0131d\u0131r. Arama index&#8217;lerinde de ayn\u0131 filtre gereklidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir de &#8220;noisy neighbor&#8221; problemi var. Tek bir b\u00fcy\u00fck m\u00fc\u015fterinin a\u011f\u0131r raporu, ayn\u0131 veritaban\u0131ndaki herkesin performans\u0131n\u0131 d\u00fc\u015f\u00fcrebilir. Tenant baz\u0131nda rate limit ve kaynak kotas\u0131 bu y\u00fczden izolasyonun bir par\u00e7as\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Multi-tenancy bir \u00f6zellik de\u011fil, sistemin her katman\u0131n\u0131 etkileyen bir varsay\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ve o varsay\u0131m\u0131n tek bir sorguda bozulmas\u0131, \u00fcr\u00fcn\u00fcn g\u00fcvenilirli\u011fini bir gecede bitirebilir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Tek veritaban\u0131, ayr\u0131 \u015fema veya ayr\u0131 veritaban\u0131. Multi-tenant mimaride izolasyon modeli nas\u0131l se\u00e7ilir ve tenant_id filtresini unutman\u0131n \u00f6n\u00fcne nas\u0131l ge\u00e7ilir?<\/p>\n","protected":false},"author":1,"featured_media":62,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-63","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mimari"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/63","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=63"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/62"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}