{"id":37270,"date":"2025-12-29T18:41:04","date_gmt":"2025-12-29T15:41:04","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=37270"},"modified":"2025-12-29T18:41:04","modified_gmt":"2025-12-29T15:41:04","slug":"ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/","title":{"rendered":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)"},"content":{"rendered":"<p><body><\/p>\n<h2>Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)<\/h2>\n<p>Adanm\u0131\u015f bir MySQL sunucusu kurmak, Ruby on Rails uygulamalar\u0131n\u0131n performans\u0131n\u0131 ve \u00f6l\u00e7eklenebilirli\u011fini art\u0131rmak i\u00e7in kritik bir ad\u0131md\u0131r. B\u00f6l\u00fcm 1&#8217;de, bu karar\u0131n ard\u0131ndaki nedenleri, temel kurulum ad\u0131mlar\u0131n\u0131 ve ilk ba\u011flant\u0131 yap\u0131land\u0131rmas\u0131n\u0131 ele alm\u0131\u015ft\u0131k. Bu ikinci b\u00f6l\u00fcmde ise, adanm\u0131\u015f MySQL sunucunuzun potansiyelini tam olarak ortaya \u00e7\u0131karacak, g\u00fcvenli\u011fini sa\u011flayacak, performans\u0131n\u0131 optimize edecek ve y\u00fcksek eri\u015filebilirlik ile yedekleme stratejilerini detayland\u0131racak ileri d\u00fczey konulara odaklanaca\u011f\u0131z. Amac\u0131m\u0131z, uygulaman\u0131z\u0131n artan y\u00fck alt\u0131nda bile kararl\u0131 ve h\u0131zl\u0131 \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flamakt\u0131r.<\/p>\n<h3>Veritaban\u0131 Sunucusunun G\u00fcvenli\u011fini Sa\u011flama<\/h3>\n<p>Verileriniz, uygulaman\u0131z\u0131n en de\u011ferli varl\u0131\u011f\u0131d\u0131r ve bu nedenle veritaban\u0131 sunucusunun g\u00fcvenli\u011fi, kurulumun en kritik a\u015famalar\u0131ndan biridir. Bir sald\u0131r\u0131 durumunda, t\u00fcm uygulaman\u0131z\u0131n ve kullan\u0131c\u0131 verilerinizin tehlikeye girmesi s\u00f6z konusu olabilir.<\/p>\n<h4>Temel G\u00fcvenlik Ad\u0131mlar\u0131<\/h4>\n<p>Yeni bir MySQL kurulumunda yap\u0131lmas\u0131 gereken ilk g\u00fcvenlik ad\u0131mlar\u0131 \u015funlard\u0131r:<\/p>\n<p>*   <strong>G\u00fc\u00e7l\u00fc <code>root<\/code> \u015eifresi Belirleme:<\/strong> MySQL kurulumu s\u0131ras\u0131nda veya sonras\u0131nda <code>mysql_secure_installation<\/code> komutunu kullanarak <code>root<\/code> kullan\u0131c\u0131s\u0131 i\u00e7in g\u00fc\u00e7l\u00fc bir \u015fifre belirlemek hayati \u00f6nem ta\u015f\u0131r. Bu komut ayr\u0131ca anonim kullan\u0131c\u0131lar\u0131 kald\u0131rma, uzaktan <code>root<\/code> eri\u015fimini devre d\u0131\u015f\u0131 b\u0131rakma ve test veritaban\u0131n\u0131 silme gibi di\u011fer temel g\u00fcvenlik ad\u0131mlar\u0131n\u0131 da otomatikle\u015ftirir.<br \/>\n*   <strong>Gereksiz Kullan\u0131c\u0131lar\u0131 Kald\u0131rma:<\/strong> MySQL, varsay\u0131lan olarak baz\u0131 test kullan\u0131c\u0131lar\u0131 veya anonim kullan\u0131c\u0131lar ile gelebilir. Bunlar\u0131 tespit edip kald\u0131rmak, potansiyel g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapat\u0131r.<\/p>\n<pre><code class=\"language-sql\">SELECT User, Host FROM mysql.user;\n    -- Anonim kullan\u0131c\u0131lar\u0131 kald\u0131rma\n    DROP USER ''@'localhost';\n    DROP USER ''@'your_hostname';\n    -- Gerekirse test veritaban\u0131n\u0131 silme\n    DROP DATABASE IF EXISTS test;\n    DELETE FROM mysql.db WHERE Db='test' OR Db='test\\_%';\n    FLUSH PRIVILEGES;<\/code><\/pre>\n<p>*   <strong>Uygulama \u0130\u00e7in \u00d6zel Kullan\u0131c\u0131 Olu\u015fturma:<\/strong> Rails uygulaman\u0131z\u0131n <code>root<\/code> kullan\u0131c\u0131s\u0131 ile veritaban\u0131na ba\u011flanmas\u0131 ciddi bir g\u00fcvenlik riskidir. Uygulaman\u0131z i\u00e7in sadece belirli veritabanlar\u0131na belirli yetkilerle eri\u015febilen \u00f6zel bir kullan\u0131c\u0131 olu\u015fturmal\u0131s\u0131n\u0131z.<\/p>\n<pre><code class=\"language-sql\">CREATE USER 'rails_app'@'localhost' IDENTIFIED BY 'cok_guclu_sifre';\n    GRANT ALL PRIVILEGES ON your_database_name.* TO 'rails_app'@'localhost';\n    FLUSH PRIVILEGES;<\/code><\/pre>\n<p>    E\u011fer Rails uygulamas\u0131 farkl\u0131 bir sunucudan ba\u011flanacaksa, <code>localhost<\/code> yerine uygulaman\u0131z\u0131n IP adresini veya alan ad\u0131n\u0131 belirtmeniz gerekir:<\/p>\n<pre><code class=\"language-sql\">CREATE USER 'rails_app'@'192.168.1.100' IDENTIFIED BY 'cok_guclu_sifre';\n    GRANT ALL PRIVILEGES ON your_database_name.* TO 'rails_app'@'192.168.1.100';\n    FLUSH PRIVILEGES;<\/code><\/pre>\n<h4>G\u00fcvenlik Duvar\u0131 Yap\u0131land\u0131rmas\u0131 (UFW\/firewalld)<\/h4>\n<p>Veritaban\u0131 sunucusunun sadece yetkili sunuculardan eri\u015filebilir olmas\u0131n\u0131 sa\u011flamak i\u00e7in bir g\u00fcvenlik duvar\u0131 kullanmak zorunludur.<\/p>\n<p>*   <strong>Linux G\u00fcvenlik Duvar\u0131:<\/strong> Ubuntu gibi Debian tabanl\u0131 sistemlerde UFW (Uncomplicated Firewall), CentOS\/RHEL gibi sistemlerde ise <code>firewalld<\/code> kullan\u0131l\u0131r.<br \/>\n    *   <strong>UFW \u00d6rne\u011fi:<\/strong><\/p>\n<pre><code class=\"language-bash\">sudo ufw enable\n        sudo ufw allow ssh # SSH eri\u015fimine izin ver\n        sudo ufw allow from 192.168.1.100 to any port 3306 # Rails sunucusu IP'sinden MySQL'e izin ver\n        sudo ufw status<\/code><\/pre>\n<p>    *   <strong>firewalld \u00d6rne\u011fi:<\/strong><\/p>\n<pre><code class=\"language-bash\">sudo firewall-cmd --zone=public --add-port=3306\/tcp --permanent # Ge\u00e7ici olarak t\u00fcm d\u00fcnyaya a\u00e7ar, dikkat!\n        sudo firewall-cmd --zone=public --add-rich-rule='rule family=\"ipv4\" source address=\"192.168.1.100\" port port=\"3306\" protocol=\"tcp\" accept' --permanent # Belirli IP'den izin ver\n        sudo firewall-cmd --reload<\/code><\/pre>\n<p>    Bu yap\u0131land\u0131rma, MySQL&#8217;in varsay\u0131lan portu olan 3306&#8217;ya sadece Rails uygulaman\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucudan gelen ba\u011flant\u0131lara izin verir. Di\u011fer t\u00fcm ba\u011flant\u0131lar engellenir.<\/p>\n<h4>SSL\/TLS ile G\u00fcvenli Ba\u011flant\u0131lar<\/h4>\n<p>Veritaban\u0131 ile uygulama sunucusu aras\u0131ndaki veri trafi\u011fini \u015fifrelemek, Man-in-the-Middle (MITM) sald\u0131r\u0131lar\u0131na kar\u015f\u0131 koruma sa\u011flar. MySQL, SSL\/TLS ba\u011flant\u0131lar\u0131n\u0131 destekler.<\/p>\n<p>*   <strong>Neden Gerekli?<\/strong> \u00d6zellikle veritaban\u0131 sunucusu ile uygulama sunucusu farkl\u0131 a\u011flarda veya genel internet \u00fczerinden ileti\u015fim kuruyorsa, ba\u011flant\u0131n\u0131n \u015fifrelenmesi kritik \u00f6neme sahiptir.<br \/>\n*   <strong>MySQL&#8217;de SSL Yap\u0131land\u0131rmas\u0131:<\/strong><br \/>\n    1.  <strong>Sertifika Olu\u015fturma:<\/strong> Kendi kendine imzal\u0131 sertifikalar veya bir Sertifika Yetkilisi&#8217;nden (CA) al\u0131nan sertifikalar kullan\u0131labilir. \u00dcretim ortam\u0131nda genellikle bir CA&#8217;dan al\u0131nan sertifikalar tercih edilir.<\/p>\n<pre><code class=\"language-bash\"># \u00d6rnek: Kendi kendine imzal\u0131 sertifika olu\u015fturma\n        openssl genrsa 2048 > ca-key.pem\n        openssl req -new -x509 -nodes -days 3650 -key ca-key.pem -out ca-cert.pem -subj \"\/CN=MyMySQLCA\"\n\n        openssl req -new -nodes -keyout server-key.pem -out server-req.pem -subj \"\/CN=db.example.com\"\n        openssl x509 -req -in server-req.pem -days 3650 -CA ca-cert.pem -CAkey ca-key.pem -CAcreateserial -out server-cert.pem\n\n        openssl req -new -nodes -keyout client-key.pem -out client-req.pem -subj \"\/CN=rails-app.example.com\"\n        openssl x509 -req -in client-req.pem -days 3650 -CA ca-cert.pem -CAkey ca-key.pem -CAcreateserial -out client-cert.pem<\/code><\/pre>\n<p>        Bu dosyalar\u0131 (ca-cert.pem, server-cert.pem, server-key.pem) MySQL sunucusuna, (ca-cert.pem, client-cert.pem, client-key.pem) Rails uygulama sunucusuna kopyalay\u0131n.<br \/>\n    2.  <strong><code>my.cnf<\/code> Ayarlar\u0131:<\/strong> MySQL sunucusunun <code>my.cnf<\/code> dosyas\u0131na (genellikle <code>\/etc\/mysql\/mysql.conf.d\/mysqld.cnf<\/code> veya <code>\/etc\/my.cnf<\/code> alt\u0131nda) a\u015fa\u011f\u0131daki sat\u0131rlar\u0131 ekleyin:<\/p>\n<pre><code class=\"language-ini\">[mysqld]\n        ssl-ca=\/path\/to\/ca-cert.pem\n        ssl-cert=\/path\/to\/server-cert.pem\n        ssl-key=\/path\/to\/server-key.pem<\/code><\/pre>\n<p>        MySQL servisini yeniden ba\u015flat\u0131n.<br \/>\n    3.  <strong>Rails Uygulamas\u0131nda SSL ile Ba\u011flanma (<code>database.yml<\/code>):<\/strong><br \/>\n        Rails uygulaman\u0131z\u0131n <code>config\/database.yml<\/code> dosyas\u0131nda <code>sslca<\/code>, <code>sslcert<\/code> ve <code>sslkey<\/code> parametrelerini belirterek g\u00fcvenli ba\u011flant\u0131 kurabilirsiniz:<\/p>\n<pre><code class=\"language-yaml\">production:\n          adapter: mysql2\n          encoding: utf8mb4\n          pool: <%= ENV.fetch(\"RAILS_MAX_THREADS\") { 5 } %>\n          database: your_database_name\n          username: rails_app\n          password: <%= ENV['DATABASE_PASSWORD'] %>\n          host: your_mysql_host_ip\n          sslca: \/path\/to\/ca-cert.pem\n          sslcert: \/path\/to\/client-cert.pem\n          sslkey: \/path\/to\/client-key.pem\n          # Veya sadece sunucunun sertifikas\u0131n\u0131 do\u011frulayarak ba\u011flant\u0131y\u0131 zorlamak i\u00e7in:\n          # sslverify: true<\/code><\/pre>\n<p>        Bu ad\u0131mlar, veritaban\u0131 ba\u011flant\u0131n\u0131z\u0131n \u015fifrelenmesini ve kimlik do\u011frulamas\u0131n\u0131 sa\u011flayarak g\u00fcvenli\u011fi \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r.<\/p>\n<h3>MySQL Performans Optimizasyonu<\/h3>\n<p>Adanm\u0131\u015f bir MySQL sunucusunun en b\u00fcy\u00fck avantajlar\u0131ndan biri, donan\u0131m kaynaklar\u0131n\u0131 veritaban\u0131 performans\u0131na \u00f6zel olarak ay\u0131rabilmektir. Ancak bu kaynaklar\u0131 do\u011fru \u015fekilde kullanmak i\u00e7in MySQL yap\u0131land\u0131rmas\u0131n\u0131 ince ayarlardan ge\u00e7irmek gerekir.<\/p>\n<h4>my.cnf Dosyas\u0131n\u0131n Yap\u0131land\u0131r\u0131lmas\u0131<\/h4>\n<p><code>my.cnf<\/code> dosyas\u0131, MySQL&#8217;in \u00e7al\u0131\u015fma \u015feklini kontrol eden ana yap\u0131land\u0131rma dosyas\u0131d\u0131r. Do\u011fru ayarlarla, sunucunuzun performans\u0131n\u0131 dramatik bir \u015fekilde art\u0131rabilirsiniz. Dosya genellikle <code>\/etc\/my.cnf<\/code>, <code>\/etc\/mysql\/my.cnf<\/code> veya <code>\/etc\/mysql\/mysql.conf.d\/mysqld.cnf<\/code> gibi konumlarda bulunur.<\/p>\n<p>*   <strong><code>innodb_buffer_pool_size<\/code>:<\/strong> Bu, InnoDB motorunun en kritik ayar\u0131d\u0131r. MySQL&#8217;in verileri ve indeksleri bellekte \u00f6nbelle\u011fe ald\u0131\u011f\u0131 aland\u0131r. Veritaban\u0131n\u0131z\u0131n tamam\u0131 veya s\u0131k eri\u015filen k\u0131s\u0131mlar\u0131 bu havuzda tutulabilirse, disk I\/O&#8217;su b\u00fcy\u00fck \u00f6l\u00e7\u00fcde azal\u0131r ve sorgular \u00e7ok daha h\u0131zl\u0131 \u00e7al\u0131\u015f\u0131r.<br \/>\n    *   <strong>Hesaplama:<\/strong> Genellikle sunucunun toplam RAM&#8217;inin %50 ila %80&#8217;i aras\u0131na ayarlan\u0131r. \u00d6rne\u011fin, 32GB RAM&#8217;e sahip bir sunucuda 16GB veya 24GB olarak ayarlanabilir.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>innodb_buffer_pool_size = 16G<\/code><br \/>\n*   <strong><code>innodb_log_file_size<\/code>:<\/strong> InnoDB redo log dosyalar\u0131n\u0131n boyutunu belirler. B\u00fcy\u00fck de\u011ferler, daha az log \u00e7evrimi ve daha iyi yazma performans\u0131 sa\u011flayabilir, ancak kilitlenme kurtarma s\u00fcresini art\u0131rabilir. Genellikle <code>innodb_buffer_pool_size<\/code>&#8216;\u0131n %10-25&#8217;i kadar olmas\u0131 \u00f6nerilir.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>innodb_log_file_size = 512M<\/code><br \/>\n*   <strong><code>max_connections<\/code>:<\/strong> Sunucuya ayn\u0131 anda ba\u011flanabilecek maksimum istemci say\u0131s\u0131n\u0131 belirler. Rails uygulaman\u0131z\u0131n ba\u011flant\u0131 havuzu boyutu ve olas\u0131 di\u011fer ba\u011flant\u0131lar (y\u00f6netim ara\u00e7lar\u0131, yedekleme vb.) g\u00f6z \u00f6n\u00fcnde bulundurularak ayarlanmal\u0131d\u0131r. \u00c7ok d\u00fc\u015f\u00fck olmas\u0131 ba\u011flant\u0131 hatalar\u0131na, \u00e7ok y\u00fcksek olmas\u0131 ise gereksiz bellek t\u00fcketimine yol a\u00e7abilir.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>max_connections = 200<\/code><br \/>\n*   <strong><code>query_cache_size<\/code>:<\/strong> MySQL&#8217;in eski s\u00fcr\u00fcmlerinde (MySQL 8.0 itibar\u0131yla kald\u0131r\u0131ld\u0131) sorgu \u00f6nbelle\u011fi kullan\u0131l\u0131rd\u0131. Ancak y\u00fcksek e\u015fzamanl\u0131l\u0131k ve s\u0131k veri de\u011fi\u015fiklikleri olan Rails uygulamalar\u0131 i\u00e7in genellikle performans d\u00fc\u015f\u00fc\u015f\u00fcne neden olur. Sorgu \u00f6nbelle\u011fi kilitlenmeleri ve ge\u00e7ersiz k\u0131lma maliyetleri nedeniyle \u00e7o\u011fu durumda kapat\u0131lmas\u0131 tavsiye edilir.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>query_cache_size = 0<\/code> (veya <code>query_cache_type = OFF<\/code>)<br \/>\n*   <strong><code>tmp_table_size<\/code> ve <code>max_heap_table_size<\/code>:<\/strong> Bellekte olu\u015fturulabilecek ge\u00e7ici tablolar\u0131n boyutunu belirler. Karma\u015f\u0131k sorgular (ORDER BY, GROUP BY, DISTINCT i\u00e7erenler) ge\u00e7ici tablolar olu\u015fturabilir. E\u011fer bu s\u0131n\u0131rlar a\u015f\u0131l\u0131rsa, tablolar diske yaz\u0131l\u0131r ve bu da performans\u0131 d\u00fc\u015f\u00fcr\u00fcr.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>tmp_table_size = 128M<\/code>, <code>max_heap_table_size = 128M<\/code><br \/>\n*   <strong><code>innodb_flush_log_at_trx_commit<\/code>:<\/strong> Veri g\u00fcvenli\u011fi ile performans aras\u0131nda bir denge sa\u011flar.<br \/>\n    *   <code>1<\/code> (varsay\u0131lan): Her i\u015flemde log diske yaz\u0131l\u0131r ve senkronize edilir. En y\u00fcksek veri g\u00fcvenli\u011fi, en d\u00fc\u015f\u00fck performans.<br \/>\n    *   <code>0<\/code>: Her saniye log diske yaz\u0131l\u0131r. En y\u00fcksek performans, kilitlenme durumunda son 1 saniyelik veri kayb\u0131 riski.<br \/>\n    *   <code>2<\/code>: Her i\u015flemde log diske yaz\u0131l\u0131r, ancak i\u015fletim sistemi taraf\u0131ndan senkronize edilmez. Kilitlenme durumunda birka\u00e7 saniyelik veri kayb\u0131 riski.<br \/>\n    \u00dcretim ortam\u0131nda genellikle <code>1<\/code> tercih edilir. Ancak y\u00fcksek yazma y\u00fck\u00fc olan ve k\u00fc\u00e7\u00fck veri kay\u0131plar\u0131n\u0131 tolere edebilen uygulamalarda <code>2<\/code> denenebilir.<br \/>\n*   <strong><code>skip-name-resolve<\/code>:<\/strong> MySQL&#8217;in istemci ba\u011flant\u0131lar\u0131n\u0131 ters DNS aramas\u0131 yapmadan kabul etmesini sa\u011flar. Bu, DNS sorunlar\u0131ndan kaynaklanan ba\u011flant\u0131 gecikmelerini \u00f6nler.<br \/>\n    *   <strong>\u00d6rnek:<\/strong> <code>skip-name-resolve<\/code><\/p>\n<p>Her de\u011fi\u015fiklikten sonra MySQL servisini yeniden ba\u015flatmay\u0131 unutmay\u0131n: <code>sudo systemctl restart mysql<\/code> veya <code>sudo service mysql restart<\/code>.<\/p>\n<h4>Disk I\/O Optimizasyonu<\/h4>\n<p>Veritaban\u0131 performans\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde disk I\/O h\u0131z\u0131na ba\u011fl\u0131d\u0131r.<\/p>\n<p>*   <strong>SSD Kullan\u0131m\u0131:<\/strong> Mekanik diskler yerine SSD (Solid State Drive) kullanmak, rastgele okuma\/yazma i\u015flemlerinde muazzam bir h\u0131z art\u0131\u015f\u0131 sa\u011flar. NVMe SSD&#8217;ler daha da y\u00fcksek performans sunar.<br \/>\n*   <strong>RAID Konfig\u00fcrasyonlar\u0131:<\/strong> Birden fazla diski bir araya getirerek performans ve\/veya veri g\u00fcvenli\u011fi sa\u011flamak i\u00e7in RAID (Redundant Array of Independent Disks) kullan\u0131l\u0131r.<br \/>\n    *   <strong>RAID 10 (1+0):<\/strong> Hem performans hem de veri g\u00fcvenli\u011fi i\u00e7in en iyi se\u00e7eneklerden biridir. Diskler aras\u0131nda verileri \u015feritler halinde da\u011f\u0131t\u0131r (RAID 0) ve her \u015feridin bir yede\u011fini tutar (RAID 1). Y\u00fcksek okuma\/yazma performans\u0131 ve tek disk ar\u0131zas\u0131na kar\u015f\u0131 tolerans sa\u011flar.<br \/>\n*   <strong>Dosya Sistemi Se\u00e7imi:<\/strong> Linux \u00fczerinde XFS veya ext4 gibi modern dosya sistemleri, veritaban\u0131 i\u015f y\u00fckleri i\u00e7in iyi performans sunar. XFS, \u00f6zellikle b\u00fcy\u00fck dosyalar ve e\u015fzamanl\u0131 I\/O i\u015flemleri i\u00e7in biraz daha iyi performans g\u00f6sterebilir.<\/p>\n<h3>Yedekleme ve Felaket Kurtarma Stratejileri<\/h3>\n<p>Veri kayb\u0131, bir uygulaman\u0131n ba\u015f\u0131na gelebilecek en k\u00f6t\u00fc senaryolardan biridir. D\u00fczenli ve g\u00fcvenilir yedeklemeler, felaket kurtarma plan\u0131n\u0131z\u0131n temelini olu\u015fturur.<\/p>\n<h4>Yedekleme T\u00fcrleri<\/h4>\n<p>MySQL i\u00e7in iki ana yedekleme t\u00fcr\u00fc vard\u0131r: mant\u0131ksal ve fiziksel.<\/p>\n<p>*   <strong>Mant\u0131ksal Yedeklemeler (<code>mysqldump<\/code>)<\/strong><br \/>\n    *   <strong>A\u00e7\u0131klama:<\/strong> Veritaban\u0131n\u0131n SQL ifadeleri (CREATE TABLE, INSERT vb.) \u015feklinde bir d\u00f6k\u00fcm\u00fcn\u00fc olu\u015fturur.<br \/>\n    *   <strong>Avantajlar:<\/strong> Veritaban\u0131 motorundan ba\u011f\u0131ms\u0131zd\u0131r, kolay ta\u015f\u0131nabilir, okunabilir ve belirli tablolar\u0131 veya verileri geri y\u00fcklemek i\u00e7in esneklik sunar.<br \/>\n    *   <strong>Dezavantajlar:<\/strong> \u00c7ok b\u00fcy\u00fck veritabanlar\u0131 i\u00e7in yava\u015f olabilir, geri y\u00fckleme s\u00fcresi uzundur, yedekleme s\u0131ras\u0131nda veritaban\u0131 kilitlenebilir (tutarl\u0131l\u0131k i\u00e7in).<br \/>\n    *   <strong>\u00d6rnek Komut:<\/strong><\/p>\n<pre><code class=\"language-bash\">mysqldump -u rails_app -p your_database_name > backup.sql\n        # T\u00fcm veritabanlar\u0131n\u0131 yedeklemek i\u00e7in\n        mysqldump -u root -p --all-databases > all_databases_backup.sql\n        # Tutarl\u0131 yedekleme i\u00e7in (InnoDB i\u00e7in)\n        mysqldump -u rails_app -p --single-transaction your_database_name > backup.sql<\/code><\/pre>\n<p>*   <strong>Fiziksel Yedeklemeler (Percona XtraBackup)<\/strong><br \/>\n    *   <strong>A\u00e7\u0131klama:<\/strong> Veritaban\u0131 dosyalar\u0131n\u0131n (InnoDB veri dosyalar\u0131, log dosyalar\u0131 vb.) do\u011frudan kopyas\u0131n\u0131 al\u0131r.<br \/>\n    *   <strong>Avantajlar:<\/strong> \u00d6zellikle b\u00fcy\u00fck veritabanlar\u0131 i\u00e7in \u00e7ok h\u0131zl\u0131d\u0131r, yedekleme s\u0131ras\u0131nda veritaban\u0131n\u0131 kilitlemez (hot backup), geri y\u00fckleme de h\u0131zl\u0131d\u0131r.<br \/>\n    *   <strong>Dezavantajlar:<\/strong> Sadece InnoDB motorunu destekler, veritaban\u0131 motoruna ve s\u00fcr\u00fcm\u00fcne ba\u011f\u0131ml\u0131d\u0131r, yedeklenmi\u015f dosyalar do\u011frudan okunamaz, geri y\u00fckleme i\u015flemi <code>mysqldump<\/code>&#8216;a g\u00f6re daha karma\u015f\u0131kt\u0131r.<br \/>\n    *   <strong>Temel Kullan\u0131m:<\/strong><\/p>\n<pre><code class=\"language-bash\"># Yedekleme\n        innobackupex --user=root --password=your_password \/path\/to\/backup\/dir\n\n        # Haz\u0131rlama (geri y\u00fcklemeden \u00f6nce)\n        innobackupex --apply-log \/path\/to\/backup\/dir\/LATEST_BACKUP_DIR\n\n        # Geri y\u00fckleme (MySQL servisi kapal\u0131yken)\n        innobackupex --copy-back \/path\/to\/backup\/dir\/LATEST_BACKUP_DIR\n        chown -R mysql:mysql \/var\/lib\/mysql # Veritaban\u0131 dizinini do\u011fru kullan\u0131c\u0131ya atama<\/code><\/pre>\n<h4>Otomatik Yedekleme ve Depolama<\/h4>\n<p>Manuel yedeklemeler hataya a\u00e7\u0131kt\u0131r. Otomatik yedekleme sistemleri kurmak hayati \u00f6neme sahiptir.<\/p>\n<p>*   <strong>Cron Job Kullan\u0131m\u0131:<\/strong> Linux&#8217;un zamanlanm\u0131\u015f g\u00f6rev y\u00f6neticisi olan <code>cron<\/code> ile d\u00fczenli yedekleme komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131labilir.<\/p>\n<pre><code class=\"language-bash\"># Her gece saat 02:00'de yedekleme\n    0 2 <em> <\/em> * mysqldump -u rails_app -p'cok_guclu_sifre' your_database_name | gzip > \/path\/to\/backups\/db_backup_$(date +\\%Y\\%m\\%d\\%H\\%M\\%S).sql.gz<\/code><\/pre>\n<p>*   <strong>Uzak Depolama:<\/strong> Yedeklemeleri veritaban\u0131 sunucusu \u00fczerinde tutmak, sunucu ar\u0131zas\u0131 durumunda veri kayb\u0131na yol a\u00e7abilir. Yedeklemelerin Amazon S3, Google Cloud Storage, Backblaze B2 gibi uzak ve g\u00fcvenli bir depolama hizmetine g\u00f6nderilmesi \u00f6nerilir. <code>s3cmd<\/code>, <code>aws cli<\/code> gibi ara\u00e7lar bu entegrasyonu kolayla\u015ft\u0131r\u0131r.<br \/>\n*   <strong>Yedekleme Testlerinin \u00d6nemi:<\/strong> Yedeklemelerinizin ger\u00e7ekten \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in d\u00fczenli olarak (\u00f6rne\u011fin ayda bir) geri y\u00fckleme testleri yapmal\u0131s\u0131n\u0131z. \u00c7al\u0131\u015fmayan bir yedek, hi\u00e7 yedek olmamas\u0131ndan daha k\u00f6t\u00fcd\u00fcr \u00e7\u00fcnk\u00fc yanl\u0131\u015f bir g\u00fcvenlik hissi yarat\u0131r.<\/p>\n<h3>Veritaban\u0131 \u0130zleme ve Analiz<\/h3>\n<p>Performans darbo\u011fazlar\u0131n\u0131 tespit etmek, olas\u0131 sorunlar\u0131 \u00f6nceden g\u00f6rmek ve sistemin sa\u011fl\u0131\u011f\u0131n\u0131 s\u00fcrekli kontrol etmek i\u00e7in veritaban\u0131 izlemesi zorunludur.<\/p>\n<h4>Neden \u0130zleme Gerekli?<\/h4>\n<p>*   <strong>Erken Uyar\u0131:<\/strong> Kaynak t\u00fckenmesi, yava\u015f sorgular veya ba\u011flant\u0131 sorunlar\u0131 gibi potansiyel sorunlar\u0131 kritik hale gelmeden \u00f6nce tespit etmenizi sa\u011flar.<br \/>\n*   <strong>Performans Darbo\u011fazlar\u0131n\u0131 Tespit Etme:<\/strong> Hangi sorgular\u0131n yava\u015f \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131, hangi kaynaklar\u0131n (CPU, bellek, disk I\/O) s\u0131n\u0131rlay\u0131c\u0131 oldu\u011funu belirlemenize yard\u0131mc\u0131 olur.<br \/>\n*   <strong>Kapasite Planlamas\u0131:<\/strong> Gelecekteki b\u00fcy\u00fcme i\u00e7in ne kadar kayna\u011fa ihtiya\u00e7 duyulaca\u011f\u0131n\u0131 tahmin etmenizi sa\u011flar.<\/p>\n<h4>\u0130zleme Ara\u00e7lar\u0131<\/h4>\n<p>\u00c7e\u015fitli ara\u00e7lar, MySQL sunucunuzu izlemenize yard\u0131mc\u0131 olabilir:<\/p>\n<p>*   <strong>Prometheus &#038; Grafana:<\/strong> Pop\u00fcler a\u00e7\u0131k kaynakl\u0131 izleme ve g\u00f6rselle\u015ftirme ara\u00e7lar\u0131d\u0131r. <code>node_exporter<\/code> ile sunucu metriklerini (CPU, bellek, disk), <code>mysqld_exporter<\/code> ile ise MySQL&#8217;e \u00f6zel metrikleri toplayabilirsiniz. Grafana ile bu metrikleri anla\u015f\u0131l\u0131r panolarda g\u00f6rselle\u015ftirebilirsiniz.<br \/>\n*   <strong>Percona Monitoring and Management (PMM):<\/strong> Percona taraf\u0131ndan geli\u015ftirilen, MySQL, PostgreSQL ve MongoDB i\u00e7in kapsaml\u0131 bir a\u00e7\u0131k kaynakl\u0131 izleme ve y\u00f6netim platformudur. Prometheus ve Grafana \u00fczerine kuruludur ve kutudan \u00e7\u0131kt\u0131\u011f\u0131 gibi bir\u00e7ok kullan\u0131\u015fl\u0131 pano ve araca sahiptir.<br \/>\n*   <strong>Bulut Sa\u011flay\u0131c\u0131lar\u0131n Kendi Ara\u00e7lar\u0131:<\/strong> AWS CloudWatch, Azure Monitor, Google Cloud Monitoring gibi bulut sa\u011flay\u0131c\u0131lar\u0131n\u0131n sundu\u011fu izleme ara\u00e7lar\u0131, bulutta bar\u0131nd\u0131r\u0131lan MySQL servisleri (\u00f6rne\u011fin AWS RDS) i\u00e7in entegre ve kolay kullan\u0131ml\u0131 \u00e7\u00f6z\u00fcmler sunar.<br \/>\n*   <strong>APM Ara\u00e7lar\u0131 (New Relic, Datadog):<\/strong> Uygulama Performans Y\u00f6netimi (APM) ara\u00e7lar\u0131, uygulaman\u0131z\u0131n veritaban\u0131 ile etkile\u015fimini izleyerek yava\u015f sorgular\u0131, veritaban\u0131 \u00e7a\u011fr\u0131 s\u00fcrelerini ve ba\u011flant\u0131 sorunlar\u0131n\u0131 tespit etmenize yard\u0131mc\u0131 olur.<\/p>\n<h4>\u0130zlenecek Temel Metrikler<\/h4>\n<p>*   <strong>CPU Kullan\u0131m\u0131:<\/strong> Veritaban\u0131 sorgular\u0131n\u0131n i\u015flemci \u00fczerindeki y\u00fck\u00fcn\u00fc g\u00f6sterir.<br \/>\n*   <strong>Bellek Kullan\u0131m\u0131:<\/strong> <code>innodb_buffer_pool_size<\/code> ve di\u011fer bellek alanlar\u0131n\u0131n ne kadar\u0131n\u0131n kullan\u0131ld\u0131\u011f\u0131n\u0131 izlemek \u00f6nemlidir.<br \/>\n*   <strong>Disk I\/O:<\/strong> Okuma\/yazma i\u015flemleri, gecikme s\u00fcreleri ve disk kuyruk uzunluklar\u0131, disk darbo\u011fazlar\u0131n\u0131 g\u00f6sterir.<br \/>\n*   <strong>Ba\u011flant\u0131 Say\u0131s\u0131:<\/strong> <code>max_connections<\/code> ayar\u0131n\u0131za ne kadar yakla\u015f\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir. Y\u00fcksek ba\u011flant\u0131 say\u0131s\u0131, uygulama veya veritaban\u0131 taraf\u0131nda sorunlara i\u015faret edebilir.<br \/>\n*   <strong>Uzun S\u00fcren Sorgular (Slow Query Log):<\/strong> Belirli bir s\u00fcreden (\u00f6rne\u011fin 1 saniye) daha uzun s\u00fcren sorgular\u0131 kaydeder. Performans sorunlar\u0131n\u0131n ana kayna\u011f\u0131d\u0131r. <code>my.cnf<\/code>&#8216;de <code>slow_query_log = 1<\/code> ve <code>long_query_time = 1<\/code> ile etkinle\u015ftirilir.<br \/>\n*   <strong>InnoDB Buffer Pool Kullan\u0131m\u0131:<\/strong> \u00d6nbellek isabet oran\u0131n\u0131 (cache hit ratio) izlemek, buffer pool boyutunun yeterli olup olmad\u0131\u011f\u0131n\u0131 anlamak i\u00e7in kritiktir.<br \/>\n*   <strong>Kilitlemeler (Deadlocks):<\/strong> \u0130ki veya daha fazla i\u015flemin birbirini beklemesi sonucu olu\u015fan kilitlenmeler. <code>SHOW ENGINE INNODB STATUS<\/code> komutu ile kontrol edilebilir.<\/p>\n<h3>Y\u00fcksek Eri\u015filebilirlik ve Okuma \u00d6l\u00e7eklendirmesi \u0130\u00e7in \u00c7o\u011faltma (Replication)<\/h3>\n<p>Tek bir veritaban\u0131 sunucusu hem bir tek hata noktas\u0131 (Single Point of Failure &#8211; SPOF) olu\u015fturur hem de okuma y\u00fck\u00fc artt\u0131\u011f\u0131nda darbo\u011faz haline gelir. MySQL \u00e7o\u011faltma, bu sorunlar\u0131 \u00e7\u00f6zmek i\u00e7in birincil y\u00f6ntemdir.<\/p>\n<h4>MySQL \u00c7o\u011faltma Temelleri<\/h4>\n<p>*   <strong>Master-Replica Mimarisi:<\/strong> Bir ana (master) sunucu t\u00fcm yazma i\u015flemlerini (INSERT, UPDATE, DELETE) al\u0131r. Bir veya daha fazla kopya (replica) sunucu, master&#8217;dan gelen de\u011fi\u015fiklikleri kopyalar ve kendi verilerini g\u00fcnceller. Replicalar genellikle okuma i\u015flemleri (SELECT) i\u00e7in kullan\u0131l\u0131r.<br \/>\n*   <strong>Asenkron \u00c7o\u011faltma:<\/strong> Master, bir i\u015flemi onaylamadan \u00f6nce replican\u0131n bu i\u015flemi uygulamas\u0131n\u0131 beklemez. Bu, master&#8217;\u0131n performans\u0131n\u0131 art\u0131r\u0131r ancak replica&#8217;n\u0131n master&#8217;dan k\u0131sa bir s\u00fcre geride kalmas\u0131na (replication lag) neden olabilir.<br \/>\n*   <strong>Binary Log&#8217;lar (Binlog):<\/strong> Master sunucu, t\u00fcm veri de\u011fi\u015fikliklerini binary log dosyalar\u0131na yazar. Replicalar bu log dosyalar\u0131n\u0131 okur ve kendi \u00fczerlerinde uygular.<\/p>\n<h4>\u00c7o\u011faltma Kurulumu<\/h4>\n<p>\u00c7o\u011faltma kurulumu detayl\u0131 bir s\u00fcre\u00e7tir, ancak temel ad\u0131mlar \u015funlard\u0131r:<\/p>\n<p>1.  <strong>Master Sunucu Yap\u0131land\u0131rmas\u0131 (<code>my.cnf<\/code>):<\/strong><\/p>\n<pre><code class=\"language-ini\">[mysqld]\n    server-id = 1 # Her sunucu i\u00e7in benzersiz bir ID\n    log_bin = mysql-bin # Binary log'lar\u0131 etkinle\u015ftir\n    binlog_do_db = your_database_name # Sadece belirli bir DB'yi \u00e7o\u011falt (iste\u011fe ba\u011fl\u0131)\n    # veya binlog_ignore_db ile belirli DB'leri hari\u00e7 tut<\/code><\/pre>\n<p>    MySQL servisini yeniden ba\u015flat\u0131n.<br \/>\n2.  <strong>Master \u00dczerinde \u00c7o\u011faltma Kullan\u0131c\u0131s\u0131 Olu\u015fturma:<\/strong><\/p>\n<pre><code class=\"language-sql\">CREATE USER 'replica_user'@'%' IDENTIFIED BY 'guclu_sifre';\n    GRANT REPLICATION SLAVE ON <em>.<\/em> TO 'replica_user'@'%';\n    FLUSH PRIVILEGES;<\/code><\/pre>\n<p>3.  <strong>Master&#8217;dan Mevcut Verinin Anl\u0131k G\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc Alma:<\/strong> Replican\u0131n ba\u015flang\u0131\u00e7 noktas\u0131 i\u00e7in master&#8217;dan bir <code>mysqldump<\/code> veya Percona XtraBackup ile yedek al\u0131n.<\/p>\n<pre><code class=\"language-bash\"># MySQL komut sat\u0131r\u0131nda, yedek almadan \u00f6nce master'\u0131n durumunu not edin:\n    FLUSH TABLES WITH READ LOCK;\n    SHOW MASTER STATUS;\n    -- Not al\u0131n: File ve Position de\u011ferleri\n    -- Ba\u015fka bir terminalde yedek al\u0131n:\n    mysqldump -u root -p --single-transaction --master-data=2 --all-databases > master_dump.sql\n    -- Yedekleme bittikten sonra kilitleri serbest b\u0131rak\u0131n:\n    UNLOCK TABLES;<\/code><\/pre>\n<p>4.  <strong>Replica Sunucu Yap\u0131land\u0131rmas\u0131 (<code>my.cnf<\/code>):<\/strong><\/p>\n<pre><code class=\"language-ini\">[mysqld]\n    server-id = 2 # Master'dan farkl\u0131 benzersiz bir ID\n    # read_only = 1 # Replican\u0131n sadece okunabilir olmas\u0131n\u0131 sa\u011flamak i\u00e7in (\u00f6nerilir)<\/code><\/pre>\n<p>    MySQL servisini yeniden ba\u015flat\u0131n.<br \/>\n5.  <strong>Replica&#8217;ya Veriyi Geri Y\u00fckleme:<\/strong> Master&#8217;dan ald\u0131\u011f\u0131n\u0131z yedek dosyay\u0131 replica sunucusuna kopyalay\u0131n ve geri y\u00fckleyin.<\/p>\n<pre><code class=\"language-bash\">mysql -u root -p < master_dump.sql<\/code><\/pre>\n<p>6.  <strong>Replica'y\u0131 Ba\u015flatma:<\/strong> Master'dan ald\u0131\u011f\u0131n\u0131z <code>File<\/code> ve <code>Position<\/code> de\u011ferlerini kullanarak replica'y\u0131 master'a ba\u011flay\u0131n.<\/p>\n<pre><code class=\"language-sql\">CHANGE MASTER TO\n      MASTER_HOST='master_ip_address',\n      MASTER_USER='replica_user',\n      MASTER_PASSWORD='guclu_sifre',\n      MASTER_LOG_FILE='not_aldiginiz_file_adi',\n      MASTER_LOG_POS=not_aldiginiz_position_degeri;\n    START SLAVE;<\/code><\/pre>\n<p>    <code>SHOW SLAVE STATUS\\G<\/code> komutu ile \u00e7o\u011faltman\u0131n durumunu kontrol edin. <code>Slave_IO_Running: Yes<\/code> ve <code>Slave_SQL_Running: Yes<\/code> olmal\u0131 ve <code>Seconds_Behind_Master<\/code> de\u011feri d\u00fc\u015f\u00fck olmal\u0131d\u0131r.<\/p>\n<h4>Rails Uygulamas\u0131nda \u00c7o\u011faltma Kullan\u0131m\u0131<\/h4>\n<p>Rails uygulamalar\u0131 genellikle varsay\u0131lan olarak tek bir veritaban\u0131 ba\u011flant\u0131s\u0131 kullan\u0131r. \u00c7o\u011faltma kullanmak i\u00e7in okuma ve yazma i\u015flemlerini ay\u0131rman\u0131z gerekir.<\/p>\n<p>*   <strong><code>database.yml<\/code>'de Okuma\/Yazma Ba\u011flant\u0131lar\u0131n\u0131 Ay\u0131rma:<\/strong> Rails 6.1 ve sonraki s\u00fcr\u00fcmler, <code>database.yml<\/code> i\u00e7inde okuma ve yazma ba\u011flant\u0131lar\u0131n\u0131 a\u00e7\u0131k\u00e7a tan\u0131mlaman\u0131za olanak tan\u0131r.<\/p>\n<pre><code class=\"language-yaml\">production:\n      adapter: mysql2\n      encoding: utf8mb4\n      pool: <%= ENV.fetch(\"RAILS_MAX_THREADS\") { 5 } %>\n      primary:\n        database: your_database_name\n        username: rails_app\n        password: <%= ENV['DATABASE_PASSWORD'] %>\n        host: master_db_ip\n      replica:\n        database: your_database_name\n        username: rails_app\n        password: <%= ENV['DATABASE_PASSWORD'] %>\n        host: replica_db_ip\n        replica: true # Bu ba\u011flant\u0131n\u0131n replica oldu\u011funu belirtir<\/code><\/pre>\n<p>    Bu yap\u0131land\u0131rma ile Rails, <code>primary<\/code> ba\u011flant\u0131s\u0131n\u0131 yazma i\u015flemleri i\u00e7in, <code>replica<\/code> ba\u011flant\u0131s\u0131n\u0131 ise okuma i\u015flemleri i\u00e7in kullanacakt\u0131r.<br \/>\n*   <strong><code>ActiveRecord::Base.connected_to<\/code> ile Rails 6.1+ Kullan\u0131m\u0131:<\/strong><br \/>\n    Rails 6.1 ile gelen <code>connected_to<\/code> metodu, belirli bir kod blo\u011funun belirli bir veritaban\u0131 rol\u00fc (primary veya replica) veya veritaban\u0131 ad\u0131 ile \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar.<\/p>\n<pre><code class=\"language-ruby\"># Varsay\u0131lan olarak yazma i\u015flemleri primary \u00fczerinde \u00e7al\u0131\u015f\u0131r\n    User.create(name: \"Ali\")\n\n    # Okuma i\u015flemleri i\u00e7in replica kullanma\n    ActiveRecord::Base.connected_to(role: :reading) do\n      User.all.to_a # Bu sorgu replica \u00fczerinde \u00e7al\u0131\u015f\u0131r\n    end\n\n    # Belirli bir replica'ya ba\u011flanma (e\u011fer birden fazla replica tan\u0131ml\u0131ysa)\n    ActiveRecord::Base.connected_to(role: :reading, shard: :replica_name) do\n      # ...\n    end<\/code><\/pre>\n<p>    Bu \u00f6zellik, okuma yo\u011funlu\u011fu olan k\u0131s\u0131mlar\u0131 (\u00f6rne\u011fin raporlar, arama sayfalar\u0131) replicalara y\u00f6nlendirerek master sunucunun y\u00fck\u00fcn\u00fc azaltman\u0131z\u0131 sa\u011flar.<br \/>\n*   <strong>Gem Kullan\u0131m\u0131 (Eski Rails S\u00fcr\u00fcmleri veya Daha Geli\u015fmi\u015f Senaryolar \u0130\u00e7in):<\/strong> <code>Octopus<\/code> gibi gem'ler, daha eski Rails s\u00fcr\u00fcmlerinde veya daha karma\u015f\u0131k \u00e7o\u011faltma\/sharding senaryolar\u0131nda okuma\/yazma ay\u0131rma yetene\u011fi sunar.<\/p>\n<h4>\u00c7o\u011faltma Gecikmesi (Replication Lag) Y\u00f6netimi<\/h4>\n<p>Asenkron \u00e7o\u011faltmada, replica'n\u0131n master'dan geri kalmas\u0131 (lag) yayg\u0131n bir durumdur.<\/p>\n<p>*   <strong>Neden Olu\u015fur?<\/strong><br \/>\n    *   <strong>Y\u00fcksek Yazma Y\u00fck\u00fc:<\/strong> Master'da \u00e7ok yo\u011fun yazma i\u015flemleri olmas\u0131.<br \/>\n    *   <strong>Replica'n\u0131n Yetersiz Kaynaklar\u0131:<\/strong> Replica sunucusunun CPU, bellek veya disk I\/O'sunun master'a yeti\u015fememesi.<br \/>\n    *   <strong>Uzun S\u00fcren Sorgular\/\u0130\u015flemler:<\/strong> Replica \u00fczerinde uzun s\u00fcren okuma sorgular\u0131 veya indeks olu\u015fturma gibi i\u015flemler \u00e7o\u011faltma i\u015flemini engelleyebilir.<br \/>\n*   <strong>Etkileri:<\/strong> Kullan\u0131c\u0131lar, master'a yaz\u0131lan veriyi replicalardan okuduklar\u0131nda g\u00fcncel olmayan verileri g\u00f6rebilirler.<br \/>\n*   <strong>\u00c7\u00f6z\u00fcmleri:<\/strong><br \/>\n    *   Replica sunucusunun kaynaklar\u0131n\u0131 art\u0131r\u0131n.<br \/>\n    *   Yava\u015f sorgular\u0131 optimize edin.<br \/>\n    *   <code>binlog_format<\/code>'\u0131 <code>ROW<\/code> olarak ayarlay\u0131n (varsay\u0131lan olmal\u0131), bu daha tutarl\u0131 \u00e7o\u011faltma sa\u011flar.<br \/>\n    *   Uygulama taraf\u0131nda, kritik okumalar i\u00e7in master'a ba\u011flanmay\u0131 zorlay\u0131n veya \u00e7o\u011faltma gecikmesini kontrol eden ve belirli bir gecikme e\u015fi\u011finin alt\u0131ndaysa replica'dan okuyan mant\u0131klar uygulay\u0131n. <code>ActiveRecord::Base.connected_to<\/code>'nun <code>replica_avoid_primary_over_time<\/code> gibi ayarlar\u0131 bu konuda yard\u0131mc\u0131 olabilir.<\/p>\n<h3>Rails Uygulamas\u0131nda Veritaban\u0131 Ba\u011flant\u0131 Y\u00f6netimi<\/h3>\n<p>Rails uygulamalar\u0131, veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 y\u00f6netmek i\u00e7in <code>ActiveRecord<\/code>'un ba\u011flant\u0131 havuzunu kullan\u0131r. Bu havuzun do\u011fru yap\u0131land\u0131r\u0131lmas\u0131, performans\u0131 ve kararl\u0131l\u0131\u011f\u0131 do\u011frudan etkiler.<\/p>\n<h4>ActiveRecord Ba\u011flant\u0131 Havuzu (Connection Pool)<\/h4>\n<p>*   <strong><code>pool<\/code> Ayar\u0131 (<code>database.yml<\/code>):<\/strong> Bu ayar, uygulaman\u0131z\u0131n veritaban\u0131na a\u00e7abilece\u011fi maksimum ba\u011flant\u0131 say\u0131s\u0131n\u0131 belirler.<\/p>\n<pre><code class=\"language-yaml\">production:\n      # ...\n      pool: <%= ENV.fetch(\"RAILS_MAX_THREADS\") { 5 } %><\/code><\/pre>\n<p>    *   <strong>Do\u011fru Havuz Boyutunu Se\u00e7me:<\/strong> Her Rails i\u015flemcisi (Puma, Unicorn worker'\u0131) kendi ba\u011flant\u0131 havuzunu y\u00f6netir. Toplam havuz boyutu, uygulama sunucular\u0131n\u0131zdaki i\u015f\u00e7i say\u0131s\u0131 (<code>worker_processes<\/code>) ile her i\u015f\u00e7inin i\u015f par\u00e7ac\u0131\u011f\u0131 say\u0131s\u0131 (<code>threads<\/code>) \u00e7arp\u0131m\u0131na e\u015fit olmal\u0131d\u0131r. \u00d6rne\u011fin, 4 worker ve her worker i\u00e7in 5 thread kullan\u0131yorsan\u0131z, <code>pool<\/code> de\u011feri en az 5 olmal\u0131d\u0131r (\u00e7\u00fcnk\u00fc her thread'in bir ba\u011flant\u0131ya ihtiyac\u0131 olabilir). MySQL'in <code>max_connections<\/code> ayar\u0131 ile uyumlu olmal\u0131d\u0131r. <code>max_connections<\/code> de\u011ferini a\u015fan bir toplam havuz boyutu, MySQL'den \"Too many connections\" hatas\u0131 alman\u0131za neden olur.<br \/>\n*   <strong>Ba\u011flant\u0131 S\u0131z\u0131nt\u0131lar\u0131 (Connection Leaks):<\/strong> Bir ba\u011flant\u0131n\u0131n havuzdan al\u0131nmas\u0131 ancak i\u015fi bittikten sonra havuza geri b\u0131rak\u0131lmamas\u0131 durumudur. Bu, havuzun bo\u015falmas\u0131na ve yeni isteklerin veritaban\u0131na ba\u011flanamamas\u0131na yol a\u00e7ar.<br \/>\n    *   <strong>Nedenleri:<\/strong> Genellikle <code>ActiveRecord::Base.connection.raw_connection<\/code> gibi d\u00fc\u015f\u00fck seviyeli API'lerin yanl\u0131\u015f kullan\u0131m\u0131 veya karma\u015f\u0131k transaction y\u00f6netimi.<br \/>\n    *   <strong>\u00d6nlenmesi:<\/strong> Ba\u011flant\u0131lar\u0131 her zaman <code>ActiveRecord::Base.connection_pool.with_connection<\/code> blo\u011fu i\u00e7inde kullan\u0131n veya <code>yield<\/code> ile ba\u011flant\u0131y\u0131 do\u011fru \u015fekilde serbest b\u0131rak\u0131n.<br \/>\n*   <strong>Ba\u011flant\u0131 Zaman A\u015f\u0131mlar\u0131:<\/strong><br \/>\n    *   <strong><code>wait_timeout<\/code> (MySQL):<\/strong> Sunucunun etkile\u015fimli olmayan ba\u011flant\u0131lar\u0131 kapatmadan \u00f6nce ne kadar bekleyece\u011fini belirler. Varsay\u0131lan\u0131 genellikle 8 saat (28800 saniye) civar\u0131ndad\u0131r.<br \/>\n    *   <strong><code>interactive_timeout<\/code> (MySQL):<\/strong> Etkile\u015fimli ba\u011flant\u0131lar i\u00e7in ayn\u0131 ayar.<br \/>\n    *   <strong><code>checkout_timeout<\/code> (Rails):<\/strong> Bir ba\u011flant\u0131n\u0131n havuzdan al\u0131nmas\u0131 i\u00e7in beklenecek s\u00fcreyi (saniye cinsinden) belirler. E\u011fer bu s\u00fcre i\u00e7inde ba\u011flant\u0131 al\u0131namazsa <code>ActiveRecord::ConnectionTimeoutError<\/code> hatas\u0131 f\u0131rlat\u0131l\u0131r.<br \/>\n    *   <strong>Ayarlama:<\/strong> <code>wait_timeout<\/code> ve <code>interactive_timeout<\/code> de\u011ferlerini Rails uygulaman\u0131z\u0131n ba\u011flant\u0131 havuzu zaman a\u015f\u0131mlar\u0131ndan daha uzun tutmak, MySQL'in ba\u011flant\u0131lar\u0131 Rails'ten habersiz kapatmas\u0131n\u0131 \u00f6nler. Genellikle Rails uygulamas\u0131n\u0131n <code>pool<\/code> boyutu ve <code>checkout_timeout<\/code> de\u011ferleri ile MySQL'in <code>wait_timeout<\/code> de\u011ferleri aras\u0131nda uyum sa\u011flanmal\u0131d\u0131r.<\/p>\n<h3>S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h3>\n<p>Adanm\u0131\u015f bir MySQL sunucusu bile zaman zaman sorunlarla kar\u015f\u0131la\u015fabilir. \u0130\u015fte baz\u0131 yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcmleri:<\/p>\n<p>*   <strong>Yava\u015f Sorgular:<\/strong><br \/>\n    <em>   <strong><code>EXPLAIN<\/code> Kullan\u0131m\u0131:<\/strong> <code>EXPLAIN SELECT <\/em> FROM users WHERE email = 'test@example.com';<\/code> komutu, MySQL'in bir sorguyu nas\u0131l y\u00fcr\u00fctt\u00fc\u011f\u00fcn\u00fc g\u00f6sterir. \u0130ndeks kullan\u0131l\u0131p kullan\u0131lmad\u0131\u011f\u0131n\u0131, tam tablo taramas\u0131 yap\u0131l\u0131p yap\u0131lmad\u0131\u011f\u0131n\u0131 anlaman\u0131za yard\u0131mc\u0131 olur.<br \/>\n    *   <strong>\u0130ndeks Optimizasyonu:<\/strong> <code>WHERE<\/code> ko\u015fullar\u0131nda, <code>JOIN<\/code> ko\u015fullar\u0131nda, <code>ORDER BY<\/code> ve <code>GROUP BY<\/code> ifadelerinde kullan\u0131lan s\u00fctunlara indeks eklemek sorgular\u0131 h\u0131zland\u0131r\u0131r.<br \/>\n    *   <strong>Sorgu Yeniden Yaz\u0131m\u0131:<\/strong> Karma\u015f\u0131k veya verimsiz sorgular\u0131 daha basit ve performansl\u0131 hale getirin. N+1 sorgu sorunlar\u0131n\u0131 \u00f6nleyin (eager loading ile <code>includes<\/code>).<br \/>\n*   <strong>Ba\u011flant\u0131 Limitlerine Ula\u015fma (<code>Too many connections<\/code>):<\/strong><br \/>\n    *   <strong><code>max_connections<\/code> Art\u0131rma:<\/strong> <code>my.cnf<\/code> dosyas\u0131ndaki <code>max_connections<\/code> de\u011ferini art\u0131r\u0131n. Ancak bu, sunucunun bellek t\u00fcketimini de art\u0131racakt\u0131r.<br \/>\n    *   <strong>Uygulama Katman\u0131nda Ba\u011flant\u0131 Havuzu Y\u00f6netimi:<\/strong> Rails uygulamas\u0131n\u0131n <code>pool<\/code> boyutunu kontrol edin ve gerekiyorsa azalt\u0131n. Ba\u011flant\u0131 s\u0131z\u0131nt\u0131lar\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<br \/>\n*   <strong>Disk Alan\u0131 T\u00fcketimi:<\/strong><br \/>\n    *   <strong>Log Dosyalar\u0131:<\/strong> MySQL binary log'lar\u0131, error log'lar\u0131 ve slow query log'lar\u0131 zamanla diskte yer kaplayabilir. Log rotasyonu (logrotate) kurarak eski log'lar\u0131 otomatik olarak silin veya s\u0131k\u0131\u015ft\u0131r\u0131n.<br \/>\n    *   <strong>Yedeklemeler:<\/strong> Eski yedekleri d\u00fczenli olarak temizleyin veya uzak depolamaya ta\u015f\u0131y\u0131n.<br \/>\n    *   <strong>Ge\u00e7ici Dosyalar:<\/strong> MySQL, baz\u0131 sorgular i\u00e7in ge\u00e7ici dosyalar olu\u015fturabilir. Disk alan\u0131 doluyorsa, bu dosyalar\u0131n nerede depoland\u0131\u011f\u0131n\u0131 ve neden \u00e7ok yer kaplad\u0131\u011f\u0131n\u0131 inceleyin.<br \/>\n    *   <strong>Veri Temizli\u011fi:<\/strong> Uygulaman\u0131zdaki gereksiz veya eski verileri (\u00f6rne\u011fin eski kullan\u0131c\u0131 oturumlar\u0131, log kay\u0131tlar\u0131) d\u00fczenli olarak temizleyin.<\/p>\n<h3>Gelecek \u00d6l\u00e7eklendirme Ad\u0131mlar\u0131<\/h3>\n<p>Adanm\u0131\u015f bir MySQL sunucusu ve \u00e7o\u011faltma, \u00e7o\u011fu Rails uygulamas\u0131 i\u00e7in yeterli \u00f6l\u00e7eklendirme sa\u011flar. Ancak uygulaman\u0131z b\u00fcy\u00fcd\u00fck\u00e7e daha ileri d\u00fczeyde \u00f6l\u00e7eklendirme tekniklerine ihtiya\u00e7 duyabilirsiniz.<\/p>\n<p>*   <strong>Daha \u0130leri \u00c7o\u011faltma Mimarileri:<\/strong><br \/>\n    *   <strong>Multi-Master \u00c7o\u011faltma:<\/strong> Birden fazla master sunucunun hem okuma hem de yazma i\u015flemlerini kabul etti\u011fi bir mimari. \u00c7at\u0131\u015fma \u00e7\u00f6z\u00fcm\u00fc gerektirebilir ve karma\u015f\u0131kt\u0131r.<br \/>\n    *   <strong>MySQL Group Replication:<\/strong> MySQL 5.7+ ile gelen, fault-tolerant bir multi-master \u00e7o\u011faltma \u00e7\u00f6z\u00fcm\u00fcd\u00fcr. Y\u00fcksek eri\u015filebilirlik ve veri tutarl\u0131l\u0131\u011f\u0131 sa\u011flar.<br \/>\n*   <strong>Veritaban\u0131 B\u00f6l\u00fcmleme (Sharding):<\/strong><br \/>\n    *   <strong>Neden Gerekli?<\/strong> Tek bir veritaban\u0131 sunucusu, ne kadar optimize edilirse edilsin, belirli bir noktadan sonra dikey olarak daha fazla \u00f6l\u00e7eklenemez (daha fazla RAM, CPU ekleyemezsiniz). Sharding, veriyi birden fazla ba\u011f\u0131ms\u0131z veritaban\u0131 sunucusuna (shard) yatay olarak da\u011f\u0131tarak bu s\u0131n\u0131r\u0131 a\u015far.<br \/>\n    *   <strong>Karma\u015f\u0131kl\u0131\u011f\u0131:<\/strong> Sharding, uygulama mimarisini \u00f6nemli \u00f6l\u00e7\u00fcde karma\u015f\u0131kla\u015ft\u0131r\u0131r. Verinin hangi shard'da oldu\u011funu belirleme, shard'lar aras\u0131 sorgular, veri ta\u015f\u0131ma ve yeniden dengeleme gibi zorluklar i\u00e7erir. Genellikle <code>ActiveRecord<\/code>'un varsay\u0131lan yeteneklerinin \u00f6tesine ge\u00e7er ve \u00f6zel \u00e7\u00f6z\u00fcmler veya gem'ler gerektirir.<br \/>\n*   <strong>Veritaban\u0131 Proxy'leri:<\/strong><br \/>\n    *   <strong>ProxySQL, MaxScale:<\/strong> Bu ara\u00e7lar, uygulama ile veritaban\u0131 sunucular\u0131 aras\u0131na bir katman ekleyerek ba\u011flant\u0131 havuzu y\u00f6netimi, sorgu y\u00f6nlendirme (okumalar\u0131 replicalara, yazmalar\u0131 master'a), y\u00fck dengeleme, g\u00fcvenlik ve sorgu filtreleme gibi geli\u015fmi\u015f \u00f6zellikler sunar. Uygulama katman\u0131ndaki karma\u015f\u0131kl\u0131\u011f\u0131 azalt\u0131rken veritaban\u0131 altyap\u0131s\u0131n\u0131n esnekli\u011fini art\u0131r\u0131r.<\/p>\n<h3>Sonu\u00e7<\/h3>\n<p>Ruby on Rails uygulamalar\u0131 i\u00e7in adanm\u0131\u015f bir MySQL sunucusu kurmak, uygulaman\u0131z\u0131n performans\u0131n\u0131 ve \u00f6l\u00e7eklenebilirli\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131racak stratejik bir yat\u0131r\u0131md\u0131r. B\u00f6l\u00fcm 1'de temel kurulumu ele al\u0131rken, bu ikinci b\u00f6l\u00fcmde sunucunun g\u00fcvenli\u011fini sa\u011flaman\u0131n, performans\u0131n\u0131 optimize etmenin, d\u00fczenli yedeklemelerle veri g\u00fcvenli\u011fini garanti alt\u0131na alman\u0131n ve \u00e7o\u011faltma ile y\u00fcksek eri\u015filebilirlik ile okuma \u00f6l\u00e7eklendirmesi sa\u011flaman\u0131n kritik ad\u0131mlar\u0131n\u0131 detayland\u0131rd\u0131k.<\/p>\n<p><code>my.cnf<\/code> dosyas\u0131ndaki ince ayarlar, do\u011fru ba\u011flant\u0131 havuzu y\u00f6netimi, s\u00fcrekli izleme ve proaktif sorun giderme, bu adanm\u0131\u015f sunucunun tam potansiyelini kullanman\u0131z i\u00e7in hayati \u00f6neme sahiptir. Unutmay\u0131n ki veritaban\u0131 y\u00f6netimi s\u00fcrekli bir s\u00fcre\u00e7tir; uygulaman\u0131z ve kullan\u0131c\u0131 taban\u0131n\u0131z b\u00fcy\u00fcd\u00fck\u00e7e, veritaban\u0131 altyap\u0131n\u0131z\u0131 da s\u00fcrekli olarak g\u00f6zden ge\u00e7irmeli, optimize etmeli ve geli\u015ftirmelisiniz. Bu makaledeki bilgiler, Rails uygulaman\u0131z\u0131n gelecekteki b\u00fcy\u00fcme ve ba\u015far\u0131 i\u00e7in sa\u011flam bir veritaban\u0131 temeline sahip olmas\u0131n\u0131 sa\u011flaman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)\nAdanm\u0131\u015f bir MySQL sunucusu kurmak, Ruby on Ra","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[138],"tags":[],"class_list":{"0":"post-37270","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-mysql","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)\" \/>\n<meta property=\"og:description\" content=\"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) Adanm\u0131\u015f bir MySQL sunucusu kurmak, Ruby on Ra\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-29T15:41:04+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"24 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)\",\"datePublished\":\"2025-12-29T15:41:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\"},\"wordCount\":3886,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"MySQL\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\",\"name\":\"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-12-29T15:41:04+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/","og_locale":"tr_TR","og_type":"article","og_title":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)","og_description":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) Adanm\u0131\u015f bir MySQL sunucusu kurmak, Ruby on Ra","og_url":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-12-29T15:41:04+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"24 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)","datePublished":"2025-12-29T15:41:04+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/"},"wordCount":3886,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["MySQL"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/","url":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/","name":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2) - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-12-29T15:41:04+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/ruby-on-rails-uygulamalari-icin-olceklendirme-adanmis-bir-mysql-sunucusu-kurulumu-bolum-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Ruby on Rails Uygulamalar\u0131 \u0130\u00e7in \u00d6l\u00e7eklendirme: Adanm\u0131\u015f Bir MySQL Sunucusu Kurulumu (B\u00f6l\u00fcm 2)"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/37270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=37270"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/37270\/revisions"}],"predecessor-version":[{"id":37271,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/37270\/revisions\/37271"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=37270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=37270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=37270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}