{"id":3671,"date":"2025-12-29T18:36:45","date_gmt":"2025-12-29T15:36:45","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/kucuk-isletme-siteleri-icin-multi-region-dns-ve-cdn-failover-mimarisi\/"},"modified":"2025-12-29T18:36:45","modified_gmt":"2025-12-29T15:36:45","slug":"kucuk-isletme-siteleri-icin-multi-region-dns-ve-cdn-failover-mimarisi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/kucuk-isletme-siteleri-icin-multi-region-dns-ve-cdn-failover-mimarisi\/","title":{"rendered":"K\u00fc\u00e7\u00fck \u0130\u015fletme Siteleri \u0130\u00e7in Multi-Region DNS ve CDN Failover Mimarisi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Kucuk_Isletme_Siteleri_Icin_Multi-Region_ve_Failover_Neden_Gundeme_Geliyor\"><span class=\"toc_number toc_depth_1\">1<\/span> K\u00fc\u00e7\u00fck \u0130\u015fletme Siteleri \u0130\u00e7in Multi-Region ve Failover Neden G\u00fcndeme Geliyor?<\/a><\/li><li><a href=\"#Temel_Kavramlar_DNS_CDN_Failover_ve_Multi-Region\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel Kavramlar: DNS, CDN, Failover ve Multi-Region<\/a><ul><li><a href=\"#DNS_seviyesinde_resim_Trafigi_hangi_origine_gonderecegiz\"><span class=\"toc_number toc_depth_2\">2.1<\/span> DNS seviyesinde resim: Trafi\u011fi hangi origin\u2019e g\u00f6nderece\u011fiz?<\/a><\/li><li><a href=\"#CDN_tarafinda_resim_Icerigi_kullaniciya_en_yakin_noktadan_sunmak\"><span class=\"toc_number toc_depth_2\">2.2<\/span> CDN taraf\u0131nda resim: \u0130\u00e7eri\u011fi kullan\u0131c\u0131ya en yak\u0131n noktadan sunmak<\/a><\/li><li><a href=\"#Failover_nedir_neyi_cozer\"><span class=\"toc_number toc_depth_2\">2.3<\/span> Failover nedir, neyi \u00e7\u00f6zer?<\/a><\/li><li><a href=\"#Multi-region_kavrami_Ayni_sitenin_birden_fazla_bolgede_yasamasi\"><span class=\"toc_number toc_depth_2\">2.4<\/span> Multi-region kavram\u0131: Ayn\u0131 sitenin birden fazla b\u00f6lgede ya\u015famas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Kisitli_Butceyle_Uygulanabilir_Multi-Region_ve_Failover_Senaryolari\"><span class=\"toc_number toc_depth_1\">3<\/span> K\u0131s\u0131tl\u0131 B\u00fct\u00e7eyle Uygulanabilir Multi-Region ve Failover Senaryolar\u0131<\/a><ul><li><a href=\"#Senaryo_1_Tek_origin_akilli_CDN_ve_basit_DNS_failover\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Senaryo 1 \u2013 Tek origin, ak\u0131ll\u0131 CDN ve basit DNS failover<\/a><\/li><li><a href=\"#Senaryo_2_Iki_farkli_bolgede_VPS_DNS_tabanli_failover\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Senaryo 2 \u2013 \u0130ki farkl\u0131 b\u00f6lgede VPS + DNS tabanl\u0131 failover<\/a><\/li><li><a href=\"#Senaryo_3_Statik_acil_durum_sitesi_CDN_uzerinden_failover\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Senaryo 3 \u2013 Statik acil durum sitesi + CDN \u00fczerinden failover<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_Katmaninda_Failover_TTL_Health_Check_ve_Multi-Provider_Stratejisi\"><span class=\"toc_number toc_depth_1\">4<\/span> DNS Katman\u0131nda Failover: TTL, Health Check ve Multi-Provider Stratejisi<\/a><ul><li><a href=\"#TTL_ayarlari_Ne_kadar_kucuk_ne_kadar_mantikli\"><span class=\"toc_number toc_depth_2\">4.1<\/span> TTL ayarlar\u0131: Ne kadar k\u00fc\u00e7\u00fck, ne kadar mant\u0131kl\u0131?<\/a><\/li><li><a href=\"#Health_check_mekanizmasi_DNS_saglayiciniz_siteyi_nasil_8220olcuyor8221\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Health check mekanizmas\u0131: DNS sa\u011flay\u0131c\u0131n\u0131z siteyi nas\u0131l &#8220;\u00f6l\u00e7\u00fcyor&#8221;?<\/a><\/li><li><a href=\"#Multi-provider_DNS_Tek_bir_DNS_saglayicisina_bagli_kalmamak\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Multi-provider DNS: Tek bir DNS sa\u011flay\u0131c\u0131s\u0131na ba\u011fl\u0131 kalmamak<\/a><\/li><\/ul><\/li><li><a href=\"#CDN_Katmaninda_Failover_Origin_Sagligi_Stale_Icerik_ve_Multi-Origin\"><span class=\"toc_number toc_depth_1\">5<\/span> CDN Katman\u0131nda Failover: Origin Sa\u011fl\u0131\u011f\u0131, Stale \u0130\u00e7erik ve Multi-Origin<\/a><ul><li><a href=\"#Origin_health_check_ve_otomatik_origin_gecisi\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Origin health check ve otomatik origin ge\u00e7i\u015fi<\/a><\/li><li><a href=\"#Stale-if-error_ve_stale-while-revalidate_ile_kesintide_bile_sayfa_gostermek\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Stale-if-error ve stale-while-revalidate ile kesintide bile sayfa g\u00f6stermek<\/a><\/li><li><a href=\"#CDN_DNS_birlikte_nasil_calisir\"><span class=\"toc_number toc_depth_2\">5.3<\/span> CDN + DNS birlikte nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Ornek_Multi-Region_DNS_CDN_Failover_Mimarisi\"><span class=\"toc_number toc_depth_1\">6<\/span> DCHost \u00dczerinde \u00d6rnek Multi-Region DNS + CDN Failover Mimarisi<\/a><ul><li><a href=\"#Adim_1_Bolgeleri_ve_sunucu_tiplerini_secmek\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Ad\u0131m 1 \u2013 B\u00f6lgeleri ve sunucu tiplerini se\u00e7mek<\/a><\/li><li><a href=\"#Adim_2_Uygulama_kopyasini_ve_veritabanini_senkron_tutmak\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Ad\u0131m 2 \u2013 Uygulama kopyas\u0131n\u0131 ve veritaban\u0131n\u0131 senkron tutmak<\/a><\/li><li><a href=\"#Adim_3_DNS_kayitlarini_failoveri_destekleyecek_sekilde_tasarlamak\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Ad\u0131m 3 \u2013 DNS kay\u0131tlar\u0131n\u0131 failover\u2019\u0131 destekleyecek \u015fekilde tasarlamak<\/a><\/li><li><a href=\"#Adim_4_CDN_onbellek_politikalarini_dogru_ayarlamak\"><span class=\"toc_number toc_depth_2\">6.4<\/span> Ad\u0131m 4 \u2013 CDN \u00f6nbellek politikalar\u0131n\u0131 do\u011fru ayarlamak<\/a><\/li><\/ul><\/li><li><a href=\"#Izleme_Test_ve_Felaket_Provalari_Kagit_Ustunde_Kalmamasini_Nasil_Saglarsiniz\"><span class=\"toc_number toc_depth_1\">7<\/span> \u0130zleme, Test ve Felaket Provalar\u0131: K\u00e2\u011f\u0131t \u00dcst\u00fcnde Kalmamas\u0131n\u0131 Nas\u0131l Sa\u011flars\u0131n\u0131z?<\/a><ul><li><a href=\"#Uptime_izleme_ve_alarm_kanallari\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Uptime izleme ve alarm kanallar\u0131<\/a><\/li><li><a href=\"#Felaket_provasi_Kablo_cekip_test_etmeden_mimari_hazir_sayilmaz\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Felaket provas\u0131: Kablo \u00e7ekip test etmeden mimari haz\u0131r say\u0131lmaz<\/a><\/li><\/ul><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_Pratik_Kontrol_Listesi\"><span class=\"toc_number toc_depth_1\">8<\/span> S\u0131k Yap\u0131lan Hatalar ve Pratik Kontrol Listesi<\/a><ul><li><a href=\"#Yaygin_hatalar\"><span class=\"toc_number toc_depth_2\">8.1<\/span> Yayg\u0131n hatalar<\/a><\/li><li><a href=\"#Basit_kontrol_listesi\"><span class=\"toc_number toc_depth_2\">8.2<\/span> Basit kontrol listesi<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_Kucuk_Isletmeler_Icin_Gercekci_Multi-Region_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7: K\u00fc\u00e7\u00fck \u0130\u015fletmeler \u0130\u00e7in Ger\u00e7ek\u00e7i Multi-Region Yol Haritas\u0131<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Kucuk_Isletme_Siteleri_Icin_Multi-Region_ve_Failover_Neden_Gundeme_Geliyor\">K\u00fc\u00e7\u00fck \u0130\u015fletme Siteleri \u0130\u00e7in Multi-Region ve Failover Neden G\u00fcndeme Geliyor?<\/span><\/h2>\n<p>K\u00fc\u00e7\u00fck bir i\u015fletme sitesi y\u00f6netirken \u00e7o\u011fu zaman \u00f6ncelik tasar\u0131m, i\u00e7erik ve reklam b\u00fct\u00e7esinde olur. Ancak pratikte m\u00fc\u015fteri \u015fik\u00e2yetlerinin \u00f6nemli bir k\u0131sm\u0131 tek bir noktaya dayan\u0131r: &#8220;Siteye giremiyorum&#8221; veya &#8220;Sayfa \u00e7ok yava\u015f a\u00e7\u0131l\u0131yor&#8221;. Bir sunucu ar\u0131zas\u0131, veri merkezi taraf\u0131ndaki bir a\u011f problemi veya beklenmeyen bir bak\u0131m \u00e7al\u0131\u015fmas\u0131; sat\u0131\u015fta olan bir e-ticaret sitesini, rezervasyon alan bir otel sitesini ya da B2B teklif formu olan bir kurumsal sayfay\u0131 dakikalar i\u00e7inde i\u015f yapamaz hale getirebilir.<\/p>\n<p>Multi-region DNS ve CDN failover mimarisi tam da bu noktada devreye giriyor. Ama\u00e7; b\u00fct\u00e7eyi zorlamadan, m\u00fcmk\u00fcn oldu\u011funca az ek bile\u015fenle, sitenizi birden fazla b\u00f6lgeye yaymak ve bir b\u00f6lge ya da sunucu sorun ya\u015fad\u0131\u011f\u0131nda trafi\u011fi otomatik olarak ayakta kalan hedefe y\u00f6nlendirmek. Yani tek bir sunucuya ve tek bir veri merkezine ba\u011f\u0131ml\u0131 kalmamak.<\/p>\n<p>DCHost taraf\u0131nda hem k\u00fc\u00e7\u00fck i\u015fletme hem de ajans m\u00fc\u015fterilerimizle yapt\u0131\u011f\u0131m\u0131z kapasite planlama ve mimari tasar\u0131m toplant\u0131lar\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ortak nokta \u015fu: Multi-region kavram\u0131 genellikle &#8220;kurumsal&#8221; ve &#8220;\u00e7ok pahal\u0131&#8221; bir \u015feymi\u015f gibi alg\u0131lan\u0131yor. Asl\u0131nda do\u011fru planland\u0131\u011f\u0131nda, iki uygun boyutlu <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> ve ak\u0131ll\u0131 bir DNS\/CDN kurgusu ile gayet eri\u015filebilir ve s\u00fcrd\u00fcr\u00fclebilir bir yap\u0131 kurmak m\u00fcmk\u00fcn. Bu yaz\u0131da tam olarak bunu, ad\u0131m ad\u0131m ve b\u00fct\u00e7eyi de d\u00fc\u015f\u00fcnerek anlataca\u011f\u0131z.<\/p>\n<h2><span id=\"Temel_Kavramlar_DNS_CDN_Failover_ve_Multi-Region\">Temel Kavramlar: DNS, CDN, Failover ve Multi-Region<\/span><\/h2>\n<h3><span id=\"DNS_seviyesinde_resim_Trafigi_hangi_origine_gonderecegiz\">DNS seviyesinde resim: Trafi\u011fi hangi origin\u2019e g\u00f6nderece\u011fiz?<\/span><\/h3>\n<p>Multi-region mimarinin kalbi DNS\u2019dir. Kullan\u0131c\u0131n\u0131n taray\u0131c\u0131s\u0131 <strong>alanadiniz.com<\/strong> i\u00e7in sorgu yapt\u0131\u011f\u0131nda, DNS yan\u0131t\u0131n\u0131z hangi IP\u2019yi ya da hangi CNAME\u2019i d\u00f6nd\u00fcr\u00fcyorsa trafik oraya gider. Dolay\u0131s\u0131yla birden fazla b\u00f6lgede sunucu veya origin kullanacaksan\u0131z, bu hedefler aras\u0131nda ak\u0131ll\u0131 se\u00e7im yapabilmek i\u00e7in DNS\u2019i stratejik kullanman\u0131z gerekir.<\/p>\n<p>DNS kay\u0131tlar\u0131n\u0131n ne anlama geldi\u011fini ve s\u0131k yap\u0131lan hatalar\u0131 daha \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/dns-kayitlari-nedir-a-aaaa-cname-mx-txt-ve-srv-rehberi\/\">A, AAAA, CNAME, MX, TXT ve di\u011fer DNS kay\u0131t t\u00fcrlerini anlatt\u0131\u011f\u0131m\u0131z rehberde<\/a> detayl\u0131 a\u00e7\u0131klam\u0131\u015ft\u0131k. Multi-region senaryosunda \u00f6zellikle A\/AAAA, CNAME ve gerekti\u011finde CAA gibi kay\u0131tlar \u00f6nem kazan\u0131r.<\/p>\n<p>Ayr\u0131ca DNS taraf\u0131nda <strong>Premium DNS, Registrar DNS ve CDN tabanl\u0131 DNS<\/strong> farklar\u0131n\u0131 bilmek kritik. Basit bir domain kay\u0131t firmas\u0131n\u0131n sundu\u011fu temel DNS ile geli\u015fmi\u015f sa\u011fl\u0131k kontrol\u00fc, co\u011frafi y\u00f6nlendirme veya a\u011f\u0131rl\u0131kl\u0131 routing sunan bir DNS altyap\u0131s\u0131 ayn\u0131 de\u011fildir. Bu farklar\u0131 <a href=\"https:\/\/www.dchost.com\/blog\/premium-dns-vs-registrar-dns-vs-cloudflare-dogru-secim-nasil-yapilir\/\">Premium DNS vs Registrar DNS vs Cloudflare kar\u015f\u0131la\u015ft\u0131rma rehberimizde<\/a> ayr\u0131nt\u0131l\u0131 olarak ele ald\u0131k; multi-region kurgusuna girmeden \u00f6nce o yaz\u0131ya da g\u00f6z atman\u0131z faydal\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"CDN_tarafinda_resim_Icerigi_kullaniciya_en_yakin_noktadan_sunmak\">CDN taraf\u0131nda resim: \u0130\u00e7eri\u011fi kullan\u0131c\u0131ya en yak\u0131n noktadan sunmak<\/span><\/h3>\n<p><strong>CDN (Content Delivery Network)<\/strong>, statik i\u00e7erikleri (g\u00f6rseller, CSS, JS, \u00e7o\u011fu zaman HTML) d\u00fcnyan\u0131n d\u00f6rt bir yan\u0131ndaki \u00f6nbellek (edge) noktalar\u0131na da\u011f\u0131t\u0131r. B\u00f6ylece kullan\u0131c\u0131, as\u0131l sunucunuza (origin) de\u011fil; kendisine en yak\u0131n CDN noktas\u0131na ba\u011flan\u0131r. Bu hem gecikmeyi azalt\u0131r hem de origin sunucunuzun \u00fczerindeki y\u00fck\u00fc hafifletir.<\/p>\n<p>CDN\u2019in ne zaman ger\u00e7ekten i\u015fe yarad\u0131\u011f\u0131n\u0131 ve hangi trafik profillerinde mant\u0131kl\u0131 oldu\u011funu merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/cdn-nedir-ne-zaman-gerekir-trafik-ve-lokasyona-gore-karar-rehberi\/\">CDN nedir, ne zaman gerekir ve trafik\/lokasyona g\u00f6re nas\u0131l karar verilir?<\/a> ba\u015fl\u0131kl\u0131 yaz\u0131m\u0131z\u0131 da mutlaka okuman\u0131z\u0131 \u00f6neririz. Multi-region failover tasarlarken, CDN\u2019i sadece h\u0131z arac\u0131 de\u011fil, ayn\u0131 zamanda ek bir <strong>dayan\u0131kl\u0131l\u0131k katman\u0131<\/strong> olarak d\u00fc\u015f\u00fcnmek gerekir.<\/p>\n<h3><span id=\"Failover_nedir_neyi_cozer\">Failover nedir, neyi \u00e7\u00f6zer?<\/span><\/h3>\n<p><strong>Failover<\/strong>, aktif bir sistem (sunucu, b\u00f6lge, origin) ar\u0131za ya\u015fad\u0131\u011f\u0131nda, trafi\u011fin otomatik olarak yedek sisteme y\u00f6nlendirilmesi s\u00fcrecidir. Burada iki kritik kavram vard\u0131r:<\/p>\n<ul>\n<li><strong>Failover s\u00fcresi:<\/strong> Ar\u0131za an\u0131ndan itibaren trafi\u011fin yeni hedefe y\u00f6nlenmesine kadar ge\u00e7en s\u00fcre.<\/li>\n<li><strong>G\u00f6zlemlenebilirlik:<\/strong> Problem oldu\u011funu nas\u0131l anl\u0131yorsunuz? DNS sa\u011flay\u0131c\u0131s\u0131n\u0131n health check\u2019i mi, CDN\u2019in origin denetimi mi, yoksa sizin uptime izleme arac\u0131n\u0131z m\u0131 alarm \u00fcretiyor?<\/li>\n<\/ul>\n<p>DNS tabanl\u0131 failover genelde <strong>dakikalar<\/strong> seviyesinde toparlanma s\u00fcresi sunar (TTL ve health check aral\u0131klar\u0131na ba\u011fl\u0131). CDN tabanl\u0131 origin failover ise do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda saniyeler mertebesine kadar inebilir.<\/p>\n<h3><span id=\"Multi-region_kavrami_Ayni_sitenin_birden_fazla_bolgede_yasamasi\">Multi-region kavram\u0131: Ayn\u0131 sitenin birden fazla b\u00f6lgede ya\u015famas\u0131<\/span><\/h3>\n<p><strong>Multi-region<\/strong>, sitenizin (veya uygulaman\u0131z\u0131n) birden fazla veri merkezinde\/b\u00f6lgede \u00e7al\u0131\u015fmas\u0131 anlam\u0131na gelir. En basit haliyle:<\/p>\n<ul>\n<li>\u0130stanbul veri merkezinde bir VPS (Region-1)<\/li>\n<li>Avrupa\u2019da veya farkl\u0131 bir \u015fehirde ikinci bir VPS (Region-2)<\/li>\n<li>Veritaban\u0131 replikasyonu veya en az\u0131ndan dosya ve yedek senkronizasyonu<\/li>\n<li>\u00dcstte DNS + CDN ile trafik y\u00f6nlendirme<\/li>\n<\/ul>\n<p>Daha b\u00fcy\u00fck yap\u0131larda co\u011frafi y\u00f6nlendirme, yazma\/okuma ayr\u0131m\u0131, aktif-aktif veritaban\u0131 k\u00fcmeleri gibi karma\u015f\u0131k \u00e7\u00f6z\u00fcmler gerekir. Bunlar\u0131 <a href=\"https:\/\/www.dchost.com\/blog\/cok-bolgeli-mimariler-nasil-kurulur-dns-geo%e2%80%91routing-ve-veritabani-replikasyonu-ile-korkusuz-felaket-dayanikliligi\/\">DNS geo-routing ve veritaban\u0131 replikasyonuyla \u00e7ok b\u00f6lgeli mimariler kurmay\u0131 anlatt\u0131\u011f\u0131m\u0131z yaz\u0131da<\/a> derinlemesine ele ald\u0131k. Bu yaz\u0131da ise k\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in daha sade ve uygun maliyetli senaryolara odaklanaca\u011f\u0131z.<\/p>\n<h2><span id=\"Kisitli_Butceyle_Uygulanabilir_Multi-Region_ve_Failover_Senaryolari\">K\u0131s\u0131tl\u0131 B\u00fct\u00e7eyle Uygulanabilir Multi-Region ve Failover Senaryolar\u0131<\/span><\/h2>\n<h3><span id=\"Senaryo_1_Tek_origin_akilli_CDN_ve_basit_DNS_failover\">Senaryo 1 \u2013 Tek origin, ak\u0131ll\u0131 CDN ve basit DNS failover<\/span><\/h3>\n<p>En d\u00fc\u015f\u00fck maliyetli \u00e7\u00f6z\u00fcm, sadece bir origin (\u00f6rne\u011fin DCHost \u00fczerinde tek VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>) kullan\u0131p, \u00fczerine ak\u0131ll\u0131 bir CDN katman\u0131 oturtmakt\u0131r. Mant\u0131k \u015fu \u015fekilde i\u015fler:<\/p>\n<ul>\n<li>T\u00fcm statik i\u00e7erik (g\u00f6rseller, CSS, JS) CDN \u00fczerinden sunulur.<\/li>\n<li>CDN, origin ile ba\u011flant\u0131 kuramazsa <strong>stale-if-error<\/strong> gibi \u00f6zelliklerle elindeki son ge\u00e7erli kopyay\u0131 kullan\u0131c\u0131ya sunmaya devam eder.<\/li>\n<li>DNS taraf\u0131nda ise k\u0131sa TTL ile (\u00f6rne\u011fin 300 sn) CDN\u2019in IP\u2019lerini veya CNAME\u2019lerini kullan\u0131rs\u0131n\u0131z.<\/li>\n<\/ul>\n<p>Bu modelde tam anlam\u0131yla multi-region olmasan\u0131z da; CDN edge noktalar\u0131 sayesinde kullan\u0131c\u0131ya <strong>co\u011frafi olarak yak\u0131n<\/strong> ve bir miktar <strong>dayan\u0131kl\u0131<\/strong> bir yap\u0131 sunmu\u015f olursunuz. Origin tamamen devre d\u0131\u015f\u0131 kal\u0131rsa, dinamik i\u015flemler (giri\u015f, sepet, \u00f6deme vb.) \u00e7al\u0131\u015fmaz; ancak en az\u0131ndan statik sayfalar (bilgilendirme, s\u0131k\u00e7a sorulan sorular, hatta basit bir bak\u0131m sayfas\u0131) CDN \u00f6nbelle\u011finden sunulmaya devam eder.<\/p>\n<p>K\u00fc\u00e7\u00fck kataloglu, nadiren g\u00fcncellenen kurumsal siteler i\u00e7in bu bile \u00e7o\u011fu zaman ciddi fark yarat\u0131r.<\/p>\n<h3><span id=\"Senaryo_2_Iki_farkli_bolgede_VPS_DNS_tabanli_failover\">Senaryo 2 \u2013 \u0130ki farkl\u0131 b\u00f6lgede VPS + DNS tabanl\u0131 failover<\/span><\/h3>\n<p>Bir ad\u0131m ileri gitmek istiyorsan\u0131z, en mant\u0131kl\u0131 ve h\u00e2l\u00e2 uygun maliyetli \u00e7\u00f6z\u00fcm \u015fudur:<\/p>\n<ul>\n<li>DCHost \u00fczerinde iki farkl\u0131 veri merkezinde\/konumda <strong>iki VPS<\/strong> kiralars\u0131n\u0131z (Region-1 ve Region-2).<\/li>\n<li>As\u0131l trafik Region-1\u2019e gider; Region-2 pasif yedek gibi davran\u0131r (aktif-pasif).<\/li>\n<li>DNS sa\u011flay\u0131c\u0131n\u0131zda her iki IP i\u00e7in de A\/AAAA kay\u0131tlar\u0131 tan\u0131mlan\u0131r ancak <strong>sa\u011fl\u0131k kontrolleri<\/strong> sadece Region-1\u2019i aktif olarak i\u015faretler.<\/li>\n<li>Region-1 down oldu\u011funda DNS kay\u0131tlar\u0131 otomatik olarak Region-2\u2019ye \u00e7evrilir.<\/li>\n<\/ul>\n<p>Bu modelin avantajlar\u0131:<\/p>\n<ul>\n<li>Ger\u00e7ek anlamda <strong>b\u00f6lgesel yedeklilik<\/strong> elde edersiniz.<\/li>\n<li>Bak\u0131m veya g\u00fcncelleme yapmak istedi\u011finizde trafi\u011fi ge\u00e7ici olarak Region-2\u2019ye alabilirsiniz.<\/li>\n<li>CDN ekledi\u011finizde her iki origin\u2019i de CDN taraf\u0131nda tan\u0131mlayarak <strong>\u00e7ift katmanl\u0131 failover<\/strong> kurabilirsiniz: Hem CDN, hem DNS gerekti\u011finde devreye girer.<\/li>\n<\/ul>\n<p>Dezavantaj\u0131 ise veritaban\u0131 ve dosya senkronizasyonu gerektirmesidir. WordPress veya benzeri PHP tabanl\u0131 uygulamalarda dosya senkronizasyonunu rsync\/cron ile, veritaban\u0131 taraf\u0131n\u0131 ise basit replikasyon ya da d\u00fczenli yedek\/restore mant\u0131\u011f\u0131 ile \u00e7\u00f6zebilirsiniz. DCHost taraf\u0131nda veritaban\u0131 replikasyonu ve senkronizasyonu konusunda daha \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/mysql-ve-postgresql-replikasyon-kurulumu-ile-vps-uzerinde-yuksek-erisilebilirlik\/\">MySQL ve PostgreSQL replikasyon rehberimizde<\/a> detayl\u0131 \u00f6rnekler payla\u015fm\u0131\u015ft\u0131k; oradaki prensipler burada da aynen ge\u00e7erli.<\/p>\n<h3><span id=\"Senaryo_3_Statik_acil_durum_sitesi_CDN_uzerinden_failover\">Senaryo 3 \u2013 Statik acil durum sitesi + CDN \u00fczerinden failover<\/span><\/h3>\n<p>Baz\u0131 k\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in iki tam kopya sunucu y\u00f6netmek fazla olabilir. Bu durumda \u015fu hibrit model olduk\u00e7a pratiktir:<\/p>\n<ul>\n<li>Ana site: DCHost \u00fczerindeki as\u0131l hosting\/VPS ortam\u0131n\u0131z (dinamik, veritaban\u0131 ve \u00f6deme sistemi olan site).<\/li>\n<li>Acil durum sitesi: Farkl\u0131 bir b\u00f6lgede, <strong>sadece statik HTML<\/strong> bar\u0131nd\u0131rd\u0131\u011f\u0131n\u0131z k\u00fc\u00e7\u00fck bir VPS veya statik hosting.<\/li>\n<li>CDN: Normalde ana origin\u2019e ba\u011fl\u0131d\u0131r, ancak origin down oldu\u011funda <strong>ikinci origin olarak statik acil durum sitesine<\/strong> failover yapar.<\/li>\n<\/ul>\n<p>Bu senaryoda as\u0131l siteniz tamamen eri\u015filemez olsa bile, kullan\u0131c\u0131lar en az\u0131ndan \u015fu bilgileri g\u00f6rebilir:<\/p>\n<ul>\n<li>Marka\/logo ve temel ileti\u015fim bilgileri<\/li>\n<li>&#8220;\u015eu anda bak\u0131m \u00e7al\u0131\u015fmas\u0131 yap\u0131yoruz&#8221; veya &#8220;Ge\u00e7ici bir teknik sorun ya\u015f\u0131yoruz&#8221; mesaj\u0131<\/li>\n<li>Telefon, e-posta veya alternatif sipari\u015f kanallar\u0131na y\u00f6nlendirme<\/li>\n<\/ul>\n<p>\u00d6zellikle B2B i\u015f yapan, sipari\u015flerini \u00e7o\u011funlukla telefon\/e-posta \u00fczerinden alan k\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in bu model, tam kesinti yerine <strong>degrade olmu\u015f ama ayakta kalan bir deneyim<\/strong> sunar ve maliyet olarak da olduk\u00e7a d\u00fc\u015f\u00fckt\u00fcr.<\/p>\n<h2><span id=\"DNS_Katmaninda_Failover_TTL_Health_Check_ve_Multi-Provider_Stratejisi\">DNS Katman\u0131nda Failover: TTL, Health Check ve Multi-Provider Stratejisi<\/span><\/h2>\n<h3><span id=\"TTL_ayarlari_Ne_kadar_kucuk_ne_kadar_mantikli\">TTL ayarlar\u0131: Ne kadar k\u00fc\u00e7\u00fck, ne kadar mant\u0131kl\u0131?<\/span><\/h3>\n<p>DNS failover\u2019\u0131n toparlanma s\u00fcresi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde <strong>TTL (Time To Live)<\/strong> de\u011ferlerine ba\u011fl\u0131d\u0131r. TTL, DNS yan\u0131t\u0131n\u0131n istemci ve ara sunucular taraf\u0131ndan ka\u00e7 saniye \u00f6nbellekte tutulaca\u011f\u0131n\u0131 belirler. \u00c7ok y\u00fcksek TTL, de\u011fi\u015fikliklerin ge\u00e7 yay\u0131lmas\u0131 demektir; \u00e7ok d\u00fc\u015f\u00fck TTL ise DNS sorgu maliyetlerini art\u0131rabilir.<\/p>\n<p>Genel pratik yakla\u015f\u0131m:<\/p>\n<ul>\n<li>Normal zamanlarda: 1200\u20133600 sn gibi daha y\u00fcksek TTL ile d\u00fc\u015f\u00fck sorgu maliyeti.<\/li>\n<li>Planl\u0131 ge\u00e7i\u015fler ve bak\u0131m \u00f6ncesinde: 300 sn hatta 120 sn gibi d\u00fc\u015f\u00fck TTL ile h\u0131zl\u0131 y\u00f6nlendirme.<\/li>\n<\/ul>\n<p>DNS TTL stratejilerini ve <strong>zero-downtime ge\u00e7i\u015f<\/strong> senaryolar\u0131n\u0131 detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">TTL stratejileri ve DNS yay\u0131l\u0131m\u0131n\u0131 h\u0131zland\u0131rma rehberimiz<\/a>, multi-region kurgusuna girerken elinizin alt\u0131nda olmas\u0131 gereken bir ba\u015fucu yaz\u0131s\u0131d\u0131r.<\/p>\n<h3><span id=\"Health_check_mekanizmasi_DNS_saglayiciniz_siteyi_nasil_8220olcuyor8221\">Health check mekanizmas\u0131: DNS sa\u011flay\u0131c\u0131n\u0131z siteyi nas\u0131l &#8220;\u00f6l\u00e7\u00fcyor&#8221;?<\/span><\/h3>\n<p>DNS tabanl\u0131 failover\u2019\u0131n \u00e7al\u0131\u015fmas\u0131 i\u00e7in DNS sa\u011flay\u0131c\u0131n\u0131z\u0131n belirli aral\u0131klarla sitenizi <strong>sa\u011fl\u0131k kontrol\u00fcne tabi tutmas\u0131<\/strong> gerekir. Bu kontroller genellikle \u015fu \u015fekilde yap\u0131l\u0131r:<\/p>\n<ul>\n<li>HTTP(S) iste\u011fi: Belirli bir URL\u2019ye (\u00f6rne\u011fin \/healthz veya ana sayfa) istek at\u0131l\u0131r; yan\u0131t kodu 200 de\u011filse sunucu sorunlu kabul edilir.<\/li>\n<li>TCP port kontrol\u00fc: \u00d6rne\u011fin 443 portu cevap vermiyorsa sunucu down say\u0131l\u0131r.<\/li>\n<li>Response time \u00f6l\u00e7\u00fcm\u00fc: Yan\u0131t s\u00fcresi belli bir e\u015fi\u011fin \u00fczerindeyse sorunlu olarak i\u015faretlenebilir.<\/li>\n<\/ul>\n<p>Sa\u011fl\u0131k kontrol\u00fc aral\u0131\u011f\u0131n\u0131 \u00e7ok s\u0131k yapmak (\u00f6rne\u011fin 5 saniyede bir) h\u0131zl\u0131 tepki sa\u011flar ama maliyeti ve yanl\u0131\u015f pozitif ihtimalini art\u0131r\u0131r. 30\u201360 saniyelik aral\u0131klar, k\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli siteler i\u00e7in genellikle dengeli bir se\u00e7imdir. Bunun \u00fczerine TTL eklenince ger\u00e7ek toparlanma s\u00fcresi ortaya \u00e7\u0131kar.<\/p>\n<h3><span id=\"Multi-provider_DNS_Tek_bir_DNS_saglayicisina_bagli_kalmamak\">Multi-provider DNS: Tek bir DNS sa\u011flay\u0131c\u0131s\u0131na ba\u011fl\u0131 kalmamak<\/span><\/h3>\n<p>&#8220;Sunucu taraf\u0131n\u0131 yedekledik ama DNS sa\u011flay\u0131c\u0131m\u0131z sorun ya\u015farsa ne olacak?&#8221; sorusu da giderek daha fazla soruluyor. Burada devreye <strong>\u00e7oklu sa\u011flay\u0131c\u0131 DNS<\/strong> mimarileri giriyor. Yani:<\/p>\n<ul>\n<li>Ayn\u0131 alan ad\u0131 i\u00e7in birden fazla DNS sa\u011flay\u0131c\u0131s\u0131nda yetkili ad sunucular\u0131n\u0131z var.<\/li>\n<li>Konfig\u00fcrasyon, kod \u00fczerinden (\u00f6rne\u011fin YAML) tutulup her iki tarafa da otomatik da\u011f\u0131t\u0131l\u0131yor.<\/li>\n<\/ul>\n<p>Bunu pratikte nas\u0131l kurabilece\u011finizi, <a href=\"https:\/\/www.dchost.com\/blog\/coklu-saglayici-dns-nasil-kurulur-octodns-ile-zero%e2%80%91downtime-gecis-ve-dayaniklilik-rehberi\/\">octoDNS ile \u00e7oklu sa\u011flay\u0131c\u0131 DNS ve zero-downtime ge\u00e7i\u015f rehberimizde<\/a> ad\u0131m ad\u0131m anlatt\u0131k. K\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in ilk a\u015famada \u015fart olmasa da, ajans olarak onlarca marka y\u00f6netenler veya uptime\u2019\u0131 kritik olan SaaS \u00fcr\u00fcnleri i\u00e7in orta vadede mutlaka d\u00fc\u015f\u00fcn\u00fclmesi gereken bir katman.<\/p>\n<h2><span id=\"CDN_Katmaninda_Failover_Origin_Sagligi_Stale_Icerik_ve_Multi-Origin\">CDN Katman\u0131nda Failover: Origin Sa\u011fl\u0131\u011f\u0131, Stale \u0130\u00e7erik ve Multi-Origin<\/span><\/h2>\n<h3><span id=\"Origin_health_check_ve_otomatik_origin_gecisi\">Origin health check ve otomatik origin ge\u00e7i\u015fi<\/span><\/h3>\n<p>Pek \u00e7ok modern CDN, birden fazla origin tan\u0131mlaman\u0131za ve bu origin\u2019ler aras\u0131nda <strong>otomatik failover<\/strong> yapman\u0131za izin verir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Origin-1: DCHost T\u00fcrkiye veri merkezindeki VPS\u2019iniz.<\/li>\n<li>Origin-2: DCHost\u2019un farkl\u0131 bir lokasyonundaki ikinci VPS\u2019iniz.<\/li>\n<\/ul>\n<p>CDN, belirledi\u011finiz health check URL\u2019sine her iki origin i\u00e7in de istek atar. Origin-1 yan\u0131t vermezse, gelen istekleri otomatik olarak Origin-2\u2019ye y\u00f6nlendirmeye ba\u015flar. Bu sayede kullan\u0131c\u0131 taraf\u0131nda DNS \u00f6nbellekleri de\u011fi\u015fmeden, <strong>saniyeler i\u00e7inde<\/strong> toparlanma sa\u011flayabilirsiniz.<\/p>\n<h3><span id=\"Stale-if-error_ve_stale-while-revalidate_ile_kesintide_bile_sayfa_gostermek\">Stale-if-error ve stale-while-revalidate ile kesintide bile sayfa g\u00f6stermek<\/span><\/h3>\n<p>CDN ve taray\u0131c\u0131 \u00f6nbelleklerinde kullan\u0131lan <strong>stale-if-error<\/strong> ve <strong>stale-while-revalidate<\/strong> direktifleri, \u00e7ok kritik bir detayd\u0131r:<\/p>\n<ul>\n<li><strong>stale-if-error:<\/strong> Origin hata veriyorsa (5xx), CDN elindeki eski (stale) kopyay\u0131 belirli bir s\u00fcre daha kullan\u0131c\u0131ya sunmaya devam eder.<\/li>\n<li><strong>stale-while-revalidate:<\/strong> CDN, kullan\u0131c\u0131ya h\u0131zl\u0131ca \u00f6nbellekteki i\u00e7eri\u011fi g\u00f6sterir, arkada origin\u2019den tazeleme iste\u011fi atar.<\/li>\n<\/ul>\n<p>Bu mekanizmalar\u0131 do\u011fru kulland\u0131\u011f\u0131n\u0131zda, k\u0131sa s\u00fcreli kesintiler veya deploy s\u0131ras\u0131nda ya\u015fanan dalgalanmalar kullan\u0131c\u0131ya \u00e7ok daha az yans\u0131r. Bu konuyu <a href=\"https:\/\/www.dchost.com\/blog\/kesinti-caninizi-sikmasin-stale-while-revalidate-ve-stale-if-error-nasil-hayat-kurtarir\/\">stale-while-revalidate ve stale-if-error\u2019un nas\u0131l hayat kurtard\u0131\u011f\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z yaz\u0131da<\/a> \u00f6rneklerle i\u015flemi\u015ftik; multi-region CDN kurgular\u0131nda da ayn\u0131 prensipler bire bir ge\u00e7erlidir.<\/p>\n<h3><span id=\"CDN_DNS_birlikte_nasil_calisir\">CDN + DNS birlikte nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p>Sa\u011flam bir failover mimarisi i\u00e7in ideal olan, <strong>CDN ve DNS\u2019in birlikte \u00e7al\u0131\u015fmas\u0131d\u0131r<\/strong>:<\/p>\n<ul>\n<li>DNS katman\u0131: Kullan\u0131c\u0131lar\u0131 global CDN a\u011f\u0131na y\u00f6nlendirir (CNAME veya A\/AAAA).<\/li>\n<li>CDN katman\u0131: Trafi\u011fi en uygun edge\u2019e, oradan da sa\u011fl\u0131kl\u0131 origin\u2019e y\u00f6nlendirir.<\/li>\n<li>Origin taraf\u0131: \u0130ki veya daha fazla b\u00f6lgede bar\u0131nd\u0131r\u0131l\u0131r (multi-region VPS\/dedicated).<\/li>\n<\/ul>\n<p>Bu \u00fc\u00e7l\u00fc yap\u0131 sayesinde, hem <strong>co\u011frafi gecikme (latency)<\/strong> optimize edilir, hem de bir katmanda sorun \u00e7\u0131ksa bile di\u011fer katmanlar olay\u0131 bir s\u00fcre telafi edebilir. DCHost \u00fczerinde kurdu\u011fumuz pek \u00e7ok y\u00fcksek eri\u015filebilirlik mimarisi tam olarak bu kombinasyon \u00fczerine in\u015fa ediliyor.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Ornek_Multi-Region_DNS_CDN_Failover_Mimarisi\">DCHost \u00dczerinde \u00d6rnek Multi-Region DNS + CDN Failover Mimarisi<\/span><\/h2>\n<h3><span id=\"Adim_1_Bolgeleri_ve_sunucu_tiplerini_secmek\">Ad\u0131m 1 \u2013 B\u00f6lgeleri ve sunucu tiplerini se\u00e7mek<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck bir i\u015fletme sitesi i\u00e7in tipik bir senaryo \u015f\u00f6yle olabilir:<\/p>\n<ul>\n<li><strong>Region-1:<\/strong> T\u00fcrkiye lokasyonlu NVMe VPS (ana origin)<\/li>\n<li><strong>Region-2:<\/strong> Avrupa veya farkl\u0131 bir T\u00fcrk veri merkezinde ikinci NVMe VPS (yedek origin)<\/li>\n<li><strong>CDN:<\/strong> Global POP a\u011f\u0131 olan bir CDN sa\u011flay\u0131c\u0131s\u0131 (statik ve HTML \u00f6nbellekleme a\u00e7\u0131k)<\/li>\n<li><strong>DNS:<\/strong> Health check ve a\u011f\u0131rl\u0131kl\u0131 routing deste\u011fi olan bir DNS altyap\u0131s\u0131<\/li>\n<\/ul>\n<p>DCHost taraf\u0131nda NVMe diskli VPS ve <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>larla bu yap\u0131n\u0131n altyap\u0131s\u0131n\u0131 kurup, \u00fczerine se\u00e7ti\u011finiz CDN ve DNS \u00e7\u00f6z\u00fcmlerini entegre ediyoruz. \u00d6nemli olan, ba\u015flang\u0131\u00e7ta a\u015f\u0131r\u0131 b\u00fcy\u00fck makinelere gitmek yerine, <strong>do\u011fru boyutland\u0131r\u0131lm\u0131\u015f<\/strong> kaynaklarla ba\u015flamak; ihtiyaca g\u00f6re CPU\/RAM\u2019i b\u00fcy\u00fctebilmek.<\/p>\n<h3><span id=\"Adim_2_Uygulama_kopyasini_ve_veritabanini_senkron_tutmak\">Ad\u0131m 2 \u2013 Uygulama kopyas\u0131n\u0131 ve veritaban\u0131n\u0131 senkron tutmak<\/span><\/h3>\n<p>\u0130ki b\u00f6lgede de \u00e7al\u0131\u015fan bir site istiyorsan\u0131z, en kritik konu <strong>veri tutarl\u0131l\u0131\u011f\u0131<\/strong>d\u0131r. Basitle\u015ftirilmi\u015f bir yakla\u015f\u0131m:<\/p>\n<ul>\n<li><strong>Dosyalar:<\/strong> Uygulama kodu ve y\u00fcklenen dosyalar i\u00e7in rsync tabanl\u0131 senkronizasyon veya git tabanl\u0131 deploy.<\/li>\n<li><strong>Veritaban\u0131:<\/strong> MySQL\/PostgreSQL replikasyonu veya d\u00fczenli yedek al\u0131p yedek sunucuya aktarma.<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin WordPress i\u00e7in:<\/p>\n<ol>\n<li>Uygulama kodunu bir git deposunda tutun ve her iki VPS\u2019e de otomatik deploy edin.<\/li>\n<li><code>wp-content\/uploads<\/code> klas\u00f6r\u00fcn\u00fc rsync ile Region-2\u2019ye d\u00fczenli e\u015fitleyin.<\/li>\n<li>MySQL\u2019i Region-1 \u2192 Region-2 replikasyon yapacak \u015fekilde kurun; Region-2\u2019yi <strong>read-only<\/strong> durumda tutun.<\/li>\n<\/ol>\n<p>Daha sonra ger\u00e7ekten aktif-aktif yazma ihtiyac\u0131 do\u011farsa, veritaban\u0131 k\u00fcmesi (cluster) gibi daha geli\u015fmi\u015f \u00e7\u00f6z\u00fcmlere ge\u00e7ilebilir; ancak k\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in \u00e7o\u011fu zaman aktif-pasif yap\u0131 yeterlidir.<\/p>\n<h3><span id=\"Adim_3_DNS_kayitlarini_failoveri_destekleyecek_sekilde_tasarlamak\">Ad\u0131m 3 \u2013 DNS kay\u0131tlar\u0131n\u0131 failover\u2019\u0131 destekleyecek \u015fekilde tasarlamak<\/span><\/h3>\n<p>DNS taraf\u0131nda tipik bir kurgu \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n<ul>\n<li><code>www.alanadiniz.com<\/code> \u2192 CNAME \u2192 <code>cdn.alanadiniz.com<\/code><\/li>\n<li><code>cdn.alanadiniz.com<\/code> \u2192 A\/AAAA \u2192 CDN\u2019in IP\u2019leri veya CNAME<\/li>\n<li>CDN\u2019in origin tan\u0131m\u0131 \u2192 Origin-1 (Region-1 VPS) ve Origin-2 (Region-2 VPS)<\/li>\n<\/ul>\n<p>E\u011fer CDN kullanm\u0131yorsan\u0131z, do\u011frudan:<\/p>\n<ul>\n<li><code>www.alanadiniz.com<\/code> \u2192 A\/AAAA \u2192 Region-1 IP (aktif) + Region-2 IP (yedek)<\/li>\n<\/ul>\n<p>Bu durumda DNS sa\u011flay\u0131c\u0131s\u0131n\u0131n panelinden:<\/p>\n<ul>\n<li>Region-1 kayd\u0131 i\u00e7in health check tan\u0131mlars\u0131n\u0131z.<\/li>\n<li>Region-2 kayd\u0131n\u0131 &#8220;standby&#8221; veya &#8220;backup&#8221; olarak i\u015faretlersiniz.<\/li>\n<li>TTL\u2019i 300\u2013600 sn band\u0131nda tutars\u0131n\u0131z.<\/li>\n<\/ul>\n<p>DNS kay\u0131tlar\u0131n\u0131 y\u00f6netirken, \u00e7oklu sa\u011flay\u0131c\u0131 stratejilerden geo-routing\u2019e kadar pek \u00e7ok geli\u015fmi\u015f tekni\u011fi <a href=\"https:\/\/www.dchost.com\/blog\/gelismis-dns-yonlendirme-nasil-akillanir-cloudflare-route-53-ile-cografi-agirlikli-ve-split%e2%80%91horizon-uzerine-sicacik-bir-yolculuk\/\">geli\u015fmi\u015f DNS y\u00f6nlendirme rehberimizde<\/a> detayl\u0131ca ele ald\u0131k. Multi-region mimari kurgularken bu tekniklerin hangisine ger\u00e7ekten ihtiyac\u0131n\u0131z oldu\u011funu oradan ilham alarak belirleyebilirsiniz.<\/p>\n<h3><span id=\"Adim_4_CDN_onbellek_politikalarini_dogru_ayarlamak\">Ad\u0131m 4 \u2013 CDN \u00f6nbellek politikalar\u0131n\u0131 do\u011fru ayarlamak<\/span><\/h3>\n<p>CDN taraf\u0131nda yapman\u0131z gereken temel ayarlar:<\/p>\n<ul>\n<li>Statik dosyalar i\u00e7in uzun s\u00fcreli cache (g\u00fcnler\/haftalar) + versiyonlama (query string veya dosya ad\u0131).<\/li>\n<li>HTML i\u00e7in k\u0131sa TTL (30\u2013300 sn) + stale-while-revalidate ile d\u00fc\u015f\u00fck riskli \u00f6nbellekleme.<\/li>\n<li>WooCommerce gibi dinamik sepet\/hesap sayfalar\u0131 i\u00e7in cache bypass kurallar\u0131.<\/li>\n<li>&#8220;Maintenance&#8221; veya acil durum sayfalar\u0131 i\u00e7in daha esnek cache politikas\u0131.<\/li>\n<\/ul>\n<p>WordPress ve WooCommerce gibi pop\u00fcler sistemler i\u00e7in CDN \u00f6nbellek kurallar\u0131n\u0131 nas\u0131l yazabilece\u011finizi, <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-icin-cdn-onbellek-kurallari-nasil-kurulur-woocommercede-html-cache-bypass-ve-edge-ayarlariyla-uctan-uca-hiz\/\">WordPress i\u00e7in CDN \u00f6nbellek kurallar\u0131 rehberimizde<\/a> ayr\u0131nt\u0131l\u0131 \u00f6rneklerle anlatt\u0131k. Multi-region mimaride de ayn\u0131 prensipler ge\u00e7erli; tek fark, arka tarafta bir de\u011fil iki origin\u2019iniz olmas\u0131.<\/p>\n<h2><span id=\"Izleme_Test_ve_Felaket_Provalari_Kagit_Ustunde_Kalmamasini_Nasil_Saglarsiniz\">\u0130zleme, Test ve Felaket Provalar\u0131: K\u00e2\u011f\u0131t \u00dcst\u00fcnde Kalmamas\u0131n\u0131 Nas\u0131l Sa\u011flars\u0131n\u0131z?<\/span><\/h2>\n<h3><span id=\"Uptime_izleme_ve_alarm_kanallari\">Uptime izleme ve alarm kanallar\u0131<\/span><\/h3>\n<p>Failover mekanizmas\u0131 kurup bir kenara b\u0131rakmak yeterli de\u011fil. Ger\u00e7ek d\u00fcnyada i\u015fe yarad\u0131\u011f\u0131ndan emin olman\u0131z i\u00e7in d\u00fczenli izleme ve test \u015fart:<\/p>\n<ul>\n<li>HTTP\/HTTPS uptime izleme ara\u00e7lar\u0131yla hem Region-1 hem Region-2 i\u00e7in ayr\u0131 kontroller kurun.<\/li>\n<li>Alarm kanallar\u0131n\u0131 (e-posta, SMS, Slack, Teams vb.) yap\u0131land\u0131r\u0131n.<\/li>\n<li>Hem ana domain (<code>www<\/code>) hem de CDN alt alan adlar\u0131n\u0131 izleyin.<\/li>\n<\/ul>\n<p>\u0130zleme kurulumuna nereden ba\u015flayaca\u011f\u0131n\u0131z\u0131 bilmiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/web-sitesi-uptime-izleme-ve-alarm-kurma-rehberi\/\">web sitesi uptime izleme ve alarm kurma rehberimiz<\/a> k\u00fc\u00e7\u00fck i\u015fletmeler i\u00e7in olduk\u00e7a uygulanabilir bir ba\u015flang\u0131\u00e7 listesi sunuyor.<\/p>\n<h3><span id=\"Felaket_provasi_Kablo_cekip_test_etmeden_mimari_hazir_sayilmaz\">Felaket provas\u0131: Kablo \u00e7ekip test etmeden mimari haz\u0131r say\u0131lmaz<\/span><\/h3>\n<p>Teoride \u00e7al\u0131\u015fan bir mimarinin pratikte de i\u015f g\u00f6rd\u00fc\u011f\u00fcnden emin olmak i\u00e7in d\u00fczenli aral\u0131klarla <strong>felaket provas\u0131<\/strong> yapman\u0131z gerekir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Region-1 VPS\u2019in web servisini (Nginx\/Apache) k\u0131sa s\u00fcreli\u011fine durdurun.<\/li>\n<li>Uptime izleme arac\u0131n\u0131z\u0131n ve DNS\/CDN providern\u0131z\u0131n nas\u0131l tepki verdi\u011fini g\u00f6zlemleyin.<\/li>\n<li>Ger\u00e7ek kullan\u0131c\u0131 deneyimini test etmek i\u00e7in farkl\u0131 lokasyonlardan manuel kontroller yap\u0131n.<\/li>\n<\/ul>\n<p>Daha \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/hosting-tarafinda-felaket-kurtarma-provasi-cpanel-ve-vps-yedeklerini-test-etme-rehberi\/\">hosting taraf\u0131nda felaket kurtarma provas\u0131 ve yedekleri test etme rehberimizde<\/a> de vurgulad\u0131\u011f\u0131m\u0131z gibi, test edilmeyen hi\u00e7bir plan ger\u00e7ek anlamda haz\u0131r de\u011fildir. Multi-region DNS ve CDN failover mimariniz i\u00e7in de ayn\u0131 kural ge\u00e7erli.<\/p>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_Pratik_Kontrol_Listesi\">S\u0131k Yap\u0131lan Hatalar ve Pratik Kontrol Listesi<\/span><\/h2>\n<h3><span id=\"Yaygin_hatalar\">Yayg\u0131n hatalar<\/span><\/h3>\n<p>Sahada en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar \u015funlar:<\/p>\n<ul>\n<li><strong>\u00c7ok y\u00fcksek TTL de\u011ferleri:<\/strong> 14400\u201386400 sn gibi TTL\u2019lerle DNS failover\u2019dan ger\u00e7ek\u00e7i bir toparlanma beklemek m\u00fcmk\u00fcn de\u011fil.<\/li>\n<li><strong>Sa\u011fl\u0131k kontrol\u00fc olmayan DNS:<\/strong> Sadece elle IP de\u011fi\u015ftirilerek &#8220;failover&#8221; yapmaya \u00e7al\u0131\u015fmak; bu pratikte genelde <strong>gecikmi\u015f manuel m\u00fcdahale<\/strong> anlam\u0131na gelir.<\/li>\n<li><strong>Veritaban\u0131 senkronizasyonunu unutarak iki region a\u00e7mak:<\/strong> Uygulama kodu kopyalan\u0131yor ama veritaban\u0131 sadece bir yerde; failover oldu\u011funda site bozuk veya eski veriyle a\u00e7\u0131l\u0131yor.<\/li>\n<li><strong>CDN cache kurallar\u0131n\u0131 yanl\u0131\u015f yazmak:<\/strong> T\u00fcm HTML\u2019i agresif cache\u2019leyip dinamik giri\u015f\/sepet sayfalar\u0131n\u0131 bo\u011fmak.<\/li>\n<li><strong>Test etmemek:<\/strong> &#8220;Kurduk, panelde g\u00f6z\u00fck\u00fcyor&#8221; noktas\u0131nda kal\u0131p ger\u00e7ek kesinti sim\u00fclasyonu yapmamak.<\/li>\n<\/ul>\n<h3><span id=\"Basit_kontrol_listesi\">Basit kontrol listesi<\/span><\/h3>\n<p>Multi-region DNS + CDN failover mimarinizi hayata ge\u00e7irirken \u015fu sorular\u0131 kendinize sorun:<\/p>\n<ul>\n<li>\u0130ki farkl\u0131 b\u00f6lgede en az birer origin sunucum var m\u0131?<\/li>\n<li>Bu origin\u2019lerin dosya ve veritaban\u0131 senkronizasyonu nas\u0131l yap\u0131l\u0131yor?<\/li>\n<li>DNS sa\u011flay\u0131c\u0131mda health check\u2019ler tan\u0131ml\u0131 m\u0131? Hangi aral\u0131kla \u00e7al\u0131\u015f\u0131yor?<\/li>\n<li>TTL de\u011ferlerim ger\u00e7ek\u00e7i failover s\u00fcreleriyle uyumlu mu?<\/li>\n<li>CDN \u00fczerinde birden fazla origin tan\u0131ml\u0131 m\u0131? Health check ve failover aktif mi?<\/li>\n<li>stale-if-error \/ stale-while-revalidate gibi direktifleri kullan\u0131yor muyum?<\/li>\n<li>Son 3 ay i\u00e7inde en az bir kez felaket provas\u0131 yapt\u0131m m\u0131?<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Kucuk_Isletmeler_Icin_Gercekci_Multi-Region_Yol_Haritasi\">Sonu\u00e7: K\u00fc\u00e7\u00fck \u0130\u015fletmeler \u0130\u00e7in Ger\u00e7ek\u00e7i Multi-Region Yol Haritas\u0131<\/span><\/h2>\n<p>Multi-region DNS ve CDN failover mimarisi kula\u011fa ilk bak\u0131\u015fta &#8220;b\u00fcy\u00fck kurumsal \u015firket i\u015fi&#8221; gibi gelebilir. Ancak do\u011fru kurguland\u0131\u011f\u0131nda, iki uygun boyutlu VPS, makul bir CDN ve ak\u0131ll\u0131 DNS ayarlar\u0131yla k\u00fc\u00e7\u00fck bir i\u015fletme sitesi i\u00e7in de gayet eri\u015filebilir hale geliyor. \u00dcstelik kazand\u0131\u011f\u0131n\u0131z \u015fey sadece kesinti anlar\u0131nda ayakta kalmak de\u011fil; ayn\u0131 zamanda daha d\u00fc\u015f\u00fck gecikme, daha \u00f6ng\u00f6r\u00fclebilir performans ve m\u00fc\u015fterinin g\u00f6z\u00fcnde <strong>profesyonel bir marka alg\u0131s\u0131<\/strong>.<\/p>\n<p>DCHost olarak biz, k\u00fc\u00e7\u00fck i\u015fletmelerden ajanslara ve SaaS projelerine kadar farkl\u0131 \u00f6l\u00e7ekte m\u00fc\u015fterilerimizle bu t\u00fcr mimarileri s\u0131k s\u0131k tasarlay\u0131p hayata ge\u00e7iriyoruz. \u00c7o\u011fu zaman ilk ad\u0131m, tek bir b\u00f6lgede d\u00fczg\u00fcn \u00e7al\u0131\u015fan bir mimariyi oturtmak; ikinci ad\u0131m ise buray\u0131 yava\u015f yava\u015f multi-region ve otomatik failover\u2019a evrimle\u015ftirmek oluyor. Yani bir gecede devasa bir yap\u0131 kurmak zorunda de\u011filsiniz, ad\u0131m ad\u0131m ilerleyebilirsiniz.<\/p>\n<p>Mevcut siteniz i\u00e7in hangi senaryonun (tek origin + CDN, iki VPS ile DNS failover, statik acil durum sitesi vb.) daha mant\u0131kl\u0131 oldu\u011funu birlikte de\u011ferlendirmek isterseniz, DCHost ekibi olarak kapasite planlama ve mimari tasar\u0131m s\u00fcrecinde yan\u0131n\u0131zday\u0131z. Trafik profilinizi, b\u00fct\u00e7enizi ve b\u00fcy\u00fcme hedeflerinizi masaya yat\u0131r\u0131p, hem cebinizi yormayan hem de ger\u00e7ek kesintilerde sizi ortada b\u0131rakmayan bir multi-region DNS ve CDN failover mimarisi kurmak m\u00fcmk\u00fcn. \u00d6nemli olan, ilk ad\u0131m\u0131 atmak ve bu konuyu &#8220;sonra bakar\u0131z&#8221; klas\u00f6r\u00fcnden \u00e7\u0131kar\u0131p ger\u00e7ek bir yol haritas\u0131na d\u00f6n\u00fc\u015ft\u00fcrmek.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 K\u00fc\u00e7\u00fck \u0130\u015fletme Siteleri \u0130\u00e7in Multi-Region ve Failover Neden G\u00fcndeme Geliyor?2 Temel Kavramlar: DNS, CDN, Failover ve Multi-Region2.1 DNS seviyesinde resim: Trafi\u011fi hangi origin\u2019e g\u00f6nderece\u011fiz?2.2 CDN taraf\u0131nda resim: \u0130\u00e7eri\u011fi kullan\u0131c\u0131ya en yak\u0131n noktadan sunmak2.3 Failover nedir, neyi \u00e7\u00f6zer?2.4 Multi-region kavram\u0131: Ayn\u0131 sitenin birden fazla b\u00f6lgede ya\u015famas\u01313 K\u0131s\u0131tl\u0131 B\u00fct\u00e7eyle Uygulanabilir Multi-Region ve Failover Senaryolar\u01313.1 Senaryo 1 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3672,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3671","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3671","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3671"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3671\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3672"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3671"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3671"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}