{"id":31589,"date":"2025-10-11T16:41:25","date_gmt":"2025-10-11T13:41:25","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=31589"},"modified":"2025-10-11T16:41:25","modified_gmt":"2025-10-11T13:41:25","slug":"apache-qpid-kurulumu-ve-yonetimi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/","title":{"rendered":"Apache Qpid Kurulumu ve Y\u00f6netimi"},"content":{"rendered":"

<\/p>\n

Apache Qpid Kurulumu ve Y\u00f6netimi<\/h2>\n

Giri\u015f<\/h2>\n

G\u00fcn\u00fcm\u00fcz\u00fcn modern uygulama mimarilerinde, mikroservisler ve da\u011f\u0131t\u0131k sistemler giderek daha fazla \u00f6nem kazanmaktad\u0131r. Bu t\u00fcr sistemlerde bile\u015fenler aras\u0131 ileti\u015fimin g\u00fcvenilir, esnek ve \u00f6l\u00e7eklenebilir bir \u015fekilde sa\u011flanmas\u0131 kritik bir gerekliliktir. Geleneksel do\u011frudan ba\u011flant\u0131lar yerine, mesaj kuyruklar\u0131 (message queues) veya mesaj arac\u0131lar\u0131 (message brokers) bu ihtiyac\u0131 kar\u015f\u0131lamak i\u00e7in ideal \u00e7\u00f6z\u00fcmler sunar. Apache Qpid, bu alanda \u00f6ne \u00e7\u0131kan g\u00fc\u00e7l\u00fc ve a\u00e7\u0131k kaynakl\u0131 bir mesaj arac\u0131s\u0131d\u0131r.<\/p>\n

Apache Qpid, geli\u015fmi\u015f mesaj kuyru\u011fu protokol\u00fc (AMQP – Advanced Message Queuing Protocol) standard\u0131n\u0131 uygulayan bir mesajla\u015fma sistemidir. AMQP, farkl\u0131 platformlar ve diller aras\u0131nda birlikte \u00e7al\u0131\u015fabilirli\u011fi sa\u011flayan a\u00e7\u0131k bir standartt\u0131r. Qpid, bu standard\u0131 temel alarak, y\u00fcksek performansl\u0131, g\u00fcvenilir ve \u00f6l\u00e7eklenebilir bir mesajla\u015fma altyap\u0131s\u0131 sunar. Finansal hizmetler, telekom\u00fcnikasyon, bulut bili\u015fim ve IoT gibi bir\u00e7ok sekt\u00f6rde, kritik i\u015f s\u00fcre\u00e7lerinde mesaj ak\u0131\u015f\u0131n\u0131 y\u00f6netmek i\u00e7in tercih edilmektedir.<\/p>\n

Bu makalede, Apache Qpid’in temel mimarisi ve kavramlar\u0131ndan ba\u015flayarak, farkl\u0131 i\u015fletim sistemleri \u00fczerinde kurulum ad\u0131mlar\u0131na, ard\u0131ndan detayl\u0131 y\u00f6netim ve yap\u0131land\u0131rma pratiklerine kadar kapsaml\u0131 bir rehber sunulacakt\u0131r. Ayr\u0131ca, Qpid’in temel kullan\u0131m senaryolar\u0131, sorun giderme ipu\u00e7lar\u0131 ve en iyi uygulamalar da ele al\u0131nacakt\u0131r. Amac\u0131m\u0131z, okuyuculara Apache Qpid’i ba\u015far\u0131l\u0131 bir \u015fekilde kurma, yap\u0131land\u0131rma ve y\u00f6netme konusunda pratik bilgiler sa\u011flamakt\u0131r.<\/p>\n

Apache Qpid Mimarisi ve Temel Kavramlar<\/h2>\n

Apache Qpid’i etkili bir \u015fekilde kullanabilmek i\u00e7in, arkas\u0131ndaki mimariyi ve temel mesajla\u015fma kavramlar\u0131n\u0131 anlamak \u00f6nemlidir. Qpid, AMQP standard\u0131n\u0131 uygulad\u0131\u011f\u0131 i\u00e7in, AMQP’nin ana bile\u015fenleri Qpid’in i\u015fleyi\u015finin merkezindedir.<\/p>\n

AMQP (Advanced Message Queuing Protocol) Nedir?<\/h3>\n

AMQP, mesaj y\u00f6nlendirme, kuyruklama, g\u00fcvenlik ve da\u011f\u0131t\u0131lm\u0131\u015f i\u015flemler i\u00e7in bir dizi \u00f6zelli\u011fi tan\u0131mlayan a\u00e7\u0131k bir uygulama katman\u0131 protokol\u00fcd\u00fcr. \u00dcretici (producer) ve t\u00fcketici (consumer) uygulamalar\u0131n\u0131n, do\u011frudan birbirleriyle ileti\u015fim kurmak yerine, bir mesaj arac\u0131s\u0131 (broker) arac\u0131l\u0131\u011f\u0131yla asenkron olarak mesaj al\u0131\u015fveri\u015fi yapmas\u0131n\u0131 sa\u011flar. Bu sayede uygulamalar birbirinden ba\u011f\u0131ms\u0131z hale gelir, hata tolerans\u0131 artar ve sistem daha \u00f6l\u00e7eklenebilir olur.<\/p>\n

Qpid Broker (Daemon\/Server)<\/h3>\n

Qpid Broker, AMQP mesajlar\u0131n\u0131 alan, y\u00f6nlendiren, depolayan ve t\u00fcketicilere da\u011f\u0131tan merkezi sunucudur. Qpid’in kalbi olup, t\u00fcm mesajla\u015fma mant\u0131\u011f\u0131n\u0131 bar\u0131nd\u0131r\u0131r. Apache Qpid projesi alt\u0131nda iki ana broker uygulamas\u0131 bulunmaktad\u0131r:
\n* Qpid C++ Broker:<\/strong> C++ ile yaz\u0131lm\u0131\u015f, genellikle y\u00fcksek performans ve d\u00fc\u015f\u00fck gecikme gerektiren durumlar i\u00e7in tercih edilen broker.
\n* Qpid Java Broker (Qpid JMS):<\/strong> Java ile yaz\u0131lm\u0131\u015f, Java ekosistemine daha entegre olan ve JMS (Java Message Service) deste\u011fi sunan broker. Bu makalede a\u011f\u0131rl\u0131kl\u0131 olarak C++ broker \u00fczerine odaklan\u0131lacakt\u0131r.<\/p>\n

Qpid Client (Producer\/Consumer)<\/h3>\n

Qpid Client, mesaj g\u00f6nderen (producer) veya mesaj alan (consumer) uygulamalard\u0131r. \u00c7e\u015fitli programlama dilleri i\u00e7in Qpid istemci k\u00fct\u00fcphaneleri mevcuttur (Python, Java, C++, Ruby, .NET vb.). Bu istemciler, AMQP protokol\u00fc \u00fczerinden broker ile ileti\u015fim kurarak mesaj al\u0131\u015fveri\u015fini ger\u00e7ekle\u015ftirir.<\/p>\n

Exchange<\/h3>\n

Exchange (de\u011fi\u015fim noktas\u0131), \u00fcreticiden gelen mesajlar\u0131 alan ve bu mesajlar\u0131 belirli kurallara g\u00f6re bir veya daha fazla kuyru\u011fa y\u00f6nlendiren bir AMQP bile\u015fenidir. Mesajlar do\u011frudan kuyruklara de\u011fil, exchange’lere g\u00f6nderilir. Qpid, farkl\u0131 y\u00f6nlendirme stratejilerine sahip \u00e7e\u015fitli exchange t\u00fcrlerini destekler:
\n* Direct Exchange:<\/strong> Mesajlar\u0131, routing key (y\u00f6nlendirme anahtar\u0131) ile birebir e\u015fle\u015fen kuyruklara y\u00f6nlendirir.
\n* Topic Exchange:<\/strong> Routing key’i bir dizi kal\u0131pla (wildcard’lar kullanarak) e\u015fle\u015ftirerek mesajlar\u0131 ilgili kuyruklara y\u00f6nlendirir.
\n* Fanout Exchange:<\/strong> Gelen t\u00fcm mesajlar\u0131, kendisine ba\u011fl\u0131 t\u00fcm kuyruklara kopyalayarak g\u00f6nderir (broadcast).
\n* Headers Exchange:<\/strong> Mesaj ba\u015fl\u0131klar\u0131ndaki (headers) de\u011ferlere g\u00f6re mesajlar\u0131 y\u00f6nlendirir.<\/p>\n

Queue<\/h3>\n

Queue (kuyruk), mesajlar\u0131n t\u00fcketiciler taraf\u0131ndan al\u0131nmay\u0131 bekledi\u011fi bir depolama alan\u0131d\u0131r. Exchange’lerden gelen mesajlar burada saklan\u0131r. Kuyruklar, mesajlar\u0131n s\u0131ras\u0131n\u0131 korur ve t\u00fcketiciler haz\u0131r oldu\u011funda mesajlar\u0131 onlara teslim eder. Kuyruklar, kal\u0131c\u0131 (durable) veya ge\u00e7ici (transient) olabilir. Kal\u0131c\u0131 kuyruklar, broker yeniden ba\u015flat\u0131lsa bile i\u00e7indeki mesajlar\u0131 korur.<\/p>\n

Binding<\/h3>\n

Binding (ba\u011flama), bir exchange ile bir kuyruk aras\u0131ndaki ba\u011flant\u0131y\u0131 tan\u0131mlar. Bu ba\u011flant\u0131, exchange’in hangi mesajlar\u0131 hangi kuyru\u011fa g\u00f6nderece\u011fini belirleyen bir routing key ile ili\u015fkilendirilir.<\/p>\n

Message<\/h3>\n

Message (mesaj), \u00fcretici ile t\u00fcketici aras\u0131nda ta\u015f\u0131nan veri birimidir. Bir mesaj genellikle iki ana b\u00f6l\u00fcmden olu\u015fur:
\n* Header (Ba\u015fl\u0131k):<\/strong> Mesaj\u0131n meta verilerini i\u00e7erir (routing key, content type, correlation ID, expiration vb.).
\n* Body (G\u00f6vde):<\/strong> Mesaj\u0131n as\u0131l y\u00fck\u00fcn\u00fc, yani g\u00f6nderilmek istenen veriyi i\u00e7erir.<\/p>\n

Virtual Hosts<\/h3>\n

Virtual Host (sanal ana bilgisayar), bir broker i\u00e7indeki mant\u0131ksal olarak izole edilmi\u015f bir ortamd\u0131r. Farkl\u0131 uygulamalar\u0131n veya departmanlar\u0131n ayn\u0131 broker \u00fczerinde \u00e7al\u0131\u015f\u0131rken birbirlerinin kaynaklar\u0131n\u0131 etkilememesini sa\u011flar. Her sanal ana bilgisayar\u0131n kendi exchange’leri, kuyruklar\u0131, kullan\u0131c\u0131lar\u0131 ve izinleri olabilir.<\/p>\n

G\u00fcvenlik (Authentication, Authorization)<\/h3>\n

Qpid, SASL (Simple Authentication and Security Layer) kullanarak kimlik do\u011frulama ve ACL (Access Control List) kullanarak yetkilendirme sa\u011flar. Bu sayede sadece yetkili kullan\u0131c\u0131lar\u0131n broker’a eri\u015fmesi ve belirli kaynaklar \u00fczerinde i\u015flem yapmas\u0131 kontrol edilebilir.<\/p>\n

Kurulum \u00d6ncesi Haz\u0131rl\u0131klar<\/h2>\n

Apache Qpid kurulumuna ba\u015flamadan \u00f6nce, sisteminizin belirli gereksinimleri kar\u015f\u0131lad\u0131\u011f\u0131ndan ve gerekli ba\u011f\u0131ml\u0131l\u0131klar\u0131n y\u00fckl\u00fc oldu\u011fundan emin olman\u0131z \u00f6nemlidir. Bu \u00f6n haz\u0131rl\u0131klar, kurulum s\u00fcrecini sorunsuz hale getirecektir.<\/p>\n

Sistem Gereksinimleri<\/h3>\n

* \u0130\u015fletim Sistemi:<\/strong> Apache Qpid, Linux tabanl\u0131 sistemlerde (Ubuntu, Debian, CentOS, RHEL, Fedora vb.) en iyi performans\u0131 g\u00f6sterir ve yayg\u0131n olarak kullan\u0131l\u0131r. Windows ve macOS \u00fczerinde de \u00e7al\u0131\u015ft\u0131r\u0131labilir ancak genellikle \u00fcretim ortamlar\u0131nda Linux tercih edilir.
\n* RAM ve CPU:<\/strong> Qpid’in bellek ve CPU kullan\u0131m\u0131, i\u015f y\u00fck\u00fcne (mesaj hacmi, kuyruk say\u0131s\u0131, ba\u011fl\u0131 istemci say\u0131s\u0131) ba\u011fl\u0131d\u0131r. K\u00fc\u00e7\u00fck kurulumlar i\u00e7in 1-2 GB RAM ve tek \u00e7ekirdekli bir CPU yeterli olabilirken, y\u00fcksek hacimli \u00fcretim ortamlar\u0131 i\u00e7in daha fazla kaynak (8 GB+ RAM, \u00e7ok \u00e7ekirdekli CPU) gerekebilir.
\n* Disk Alan\u0131:<\/strong> Mesaj kal\u0131c\u0131l\u0131\u011f\u0131 (persistence) kullan\u0131l\u0131yorsa, mesajlar\u0131n depolanaca\u011f\u0131 disk alan\u0131 gereklidir. Disk performans\u0131 da mesaj ak\u0131\u015f\u0131 i\u00e7in kritik olabilir.<\/p>\n

Ba\u011f\u0131ml\u0131l\u0131klar<\/h3>\n

Qpid’in hangi s\u00fcr\u00fcm\u00fcn\u00fc ve hangi bile\u015fenlerini kurdu\u011funuza ba\u011fl\u0131 olarak ba\u011f\u0131ml\u0131l\u0131klar de\u011fi\u015febilir. C++ broker i\u00e7in tipik ba\u011f\u0131ml\u0131l\u0131klar \u015funlard\u0131r:
\n* C++ Derleyici:<\/strong> GCC (GNU Compiler Collection) veya Clang gibi bir C++ derleyicisi (kaynaktan derleme yap\u0131l\u0131yorsa).
\n* Boost K\u00fct\u00fcphaneleri:<\/strong> Qpid C++ broker’\u0131 Boost k\u00fct\u00fcphanelerini yo\u011fun olarak kullan\u0131r.
\n* OpenSSL:<\/strong> G\u00fcvenli ileti\u015fim (SSL\/TLS) i\u00e7in gereklidir.
\n* CMake:<\/strong> Kaynaktan derleme i\u00e7in bir yap\u0131land\u0131rma arac\u0131.
\n* Python:<\/strong> Qpid y\u00f6netim ara\u00e7lar\u0131 (qpid-config, qpid-tool) Python ile yaz\u0131lm\u0131\u015ft\u0131r.<\/p>\n

G\u00fcvenlik Duvar\u0131 Ayarlar\u0131<\/h3>\n

Qpid broker varsay\u0131lan olarak 5672 (AMQP) ve 5671 (AMQP over TLS) portlar\u0131n\u0131 kullan\u0131r. \u0130stemcilerin broker’a ba\u011flanabilmesi i\u00e7in bu portlar\u0131n g\u00fcvenlik duvar\u0131nda a\u00e7\u0131k olmas\u0131 gerekir.
\n* Linux (ufw\/firewalld):<\/strong><\/p>\n

# Ubuntu\/Debian i\u00e7in ufw\n    sudo ufw allow 5672\/tcp\n    sudo ufw allow 5671\/tcp\n    sudo ufw reload\n\n    # CentOS\/RHEL\/Fedora i\u00e7in firewalld\n    sudo firewall-cmd --add-port=5672\/tcp --permanent\n    sudo firewall-cmd --add-port=5671\/tcp --permanent\n    sudo firewall-cmd --reload<\/code><\/pre>\n
Apache Qpid Kurulumu<\/h2>\n
Apache Qpid’in kurulumu, kullan\u0131lan i\u015fletim sistemine ve tercih edilen broker t\u00fcr\u00fcne g\u00f6re de\u011fi\u015fiklik g\u00f6sterir. Bu b\u00f6l\u00fcmde, Qpid C++ broker’\u0131n yayg\u0131n Linux da\u011f\u0131t\u0131mlar\u0131 \u00fczerindeki kurulumunu ve Python istemci kurulumunu ele alaca\u011f\u0131z.<\/p>\n
Qpid Broker (C++ tabanl\u0131) Kurulumu<\/h3>\n
Qpid C++ broker, genellikle qpid-broker<\/code> paketi olarak da\u011f\u0131t\u0131l\u0131r.<\/p>\n
Linux (Debian\/Ubuntu) \u00dczerine Kurulum<\/h4>\n
Debian ve Ubuntu tabanl\u0131 sistemlerde APT paket y\u00f6neticisi kullan\u0131larak kurulum olduk\u00e7a basittir.<\/p>\n
1.  Paket Listesini G\u00fcncelleme:<\/strong><\/p>\n
sudo apt update<\/code><\/pre>\n
2.  Qpid Broker ve Ara\u00e7lar\u0131 Kurulumu:<\/strong>
\n    qpid-broker<\/code> paketi ana broker’\u0131 i\u00e7erirken, qpid-tools<\/code> paketi y\u00f6netim ara\u00e7lar\u0131n\u0131 (qpid-config, qpid-tool) sa\u011flar.<\/p>\n
sudo apt install qpid-broker qpid-tools<\/code><\/pre>\n
3.  Servisi Ba\u015flatma ve Etkinle\u015ftirme:<\/strong>
\n    Kurulumdan sonra servis otomatik olarak ba\u015flamayabilir. systemd<\/code> kullanarak servisi ba\u015flatabilir ve sistem ba\u015flang\u0131c\u0131nda otomatik \u00e7al\u0131\u015facak \u015fekilde etkinle\u015ftirebilirsiniz.<\/p>\n
sudo systemctl start qpid-broker\n    sudo systemctl enable qpid-broker\n    sudo systemctl status qpid-broker<\/code><\/pre>\n
    Durum kontrol\u00fc ile servisin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun.<\/p>\n
Linux (RHEL\/CentOS\/Fedora) \u00dczerine Kurulum<\/h4>\n
Red Hat tabanl\u0131 sistemlerde (CentOS, RHEL, Fedora) DNF veya YUM paket y\u00f6neticisi kullan\u0131l\u0131r.<\/p>\n
1.  Paket Listesini G\u00fcncelleme:<\/strong><\/p>\n
sudo dnf update # Fedora 22+\n    sudo yum update # CentOS\/RHEL 7<\/code><\/pre>\n
2.  Qpid Broker ve Ara\u00e7lar\u0131 Kurulumu:<\/strong><\/p>\n
sudo dnf install qpid-broker qpid-tools # Fedora 22+\n    sudo yum install qpid-broker qpid-tools # CentOS\/RHEL 7<\/code><\/pre>\n
3.  Servisi Ba\u015flatma ve Etkinle\u015ftirme:<\/strong><\/p>\n
sudo systemctl start qpid-broker\n    sudo systemctl enable qpid-broker\n    sudo systemctl status qpid-broker<\/code><\/pre>\n
    Servisin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n
Kaynaktan Derleyerek Kurulum (Opsiyonel)<\/h4>\n
Paket y\u00f6neticilerinde bulunmayan daha yeni bir Qpid s\u00fcr\u00fcm\u00fcn\u00fc kullanmak veya \u00f6zel yap\u0131land\u0131rmalar yapmak istiyorsan\u0131z, kaynaktan derleme yapabilirsiniz. Bu y\u00f6ntem daha karma\u015f\u0131kt\u0131r ve gerekli ba\u011f\u0131ml\u0131l\u0131klar\u0131n manuel olarak y\u00fcklenmesini gerektirir.<\/p>\n
1.  Gerekli Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Kurma:<\/strong>
\n    *   Derleyici:<\/strong> build-essential<\/code> (Ubuntu) veya Development Tools<\/code> (CentOS\/RHEL)
\n    *   CMake:<\/strong> cmake<\/code>
\n    *   Boost:<\/strong> libboost-all-dev<\/code> (Ubuntu) veya boost-devel<\/code> (CentOS\/RHEL)
\n    *   OpenSSL:<\/strong> libssl-dev<\/code> (Ubuntu) veya openssl-devel<\/code> (CentOS\/RHEL)
\n    *   Python Geli\u015ftirme Ba\u015fl\u0131klar\u0131:<\/strong> python3-dev<\/code> (Ubuntu) veya python3-devel<\/code> (CentOS\/RHEL)
\n    *   Di\u011fer olas\u0131 ba\u011f\u0131ml\u0131l\u0131klar: libtool<\/code>, libsasl2-dev<\/code> vb.<\/p>\n
# Ubuntu\/Debian \u00f6rne\u011fi\n    sudo apt install build-essential cmake libboost-all-dev libssl-dev python3-dev libsasl2-dev libtool<\/code><\/pre>\n
2.  Qpid Kaynak Kodunu \u0130ndirme:<\/strong>
\n    Apache Qpid’in resmi web sitesinden (qpid.apache.org) veya Apache SVN\/Git deposundan kaynak kodunu indirin.<\/p>\n
wget https:\/\/downloads.apache.org\/qpid\/proton\/0.38.0\/qpid-broker-1.39.0.tar.gz # \u00d6rnek s\u00fcr\u00fcm\n    tar -xvf qpid-broker-1.39.0.tar.gz\n    cd qpid-broker-1.39.0<\/code><\/pre>\n
3.  Derleme ve Kurulum:<\/strong><\/p>\n
mkdir build\n    cd build\n    cmake .. # Gerekirse -DCMAKE_INSTALL_PREFIX=\/opt\/qpid gibi bir kurulum yolu belirtebilirsiniz.\n    make\n    sudo make install<\/code><\/pre>\n
    Bu ad\u0131mlar, Qpid broker’\u0131 sisteminize kuracakt\u0131r. Kurulum yolunu CMAKE_INSTALL_PREFIX<\/code> ile \u00f6zelle\u015ftirmediyseniz, genellikle \/usr\/local<\/code> alt\u0131na kurulur.<\/p>\n
Qpid Python Client Kurulumu<\/h3>\n
Python ile Qpid broker’a ba\u011flanmak ve mesajla\u015fma yapmak i\u00e7in qpid-proton<\/code> veya eski qpid-messaging<\/code> k\u00fct\u00fcphanelerini kullanabilirsiniz. qpid-proton<\/code> daha modern ve AMQP 1.0 standard\u0131n\u0131 destekler.<\/p>\n
1.  pip Kurulumu:<\/strong>
\n    E\u011fer sisteminizde pip<\/code> kurulu de\u011filse kurun:<\/p>\n
sudo apt install python3-pip # Ubuntu\/Debian\n    sudo dnf install python3-pip # CentOS\/RHEL\/Fedora<\/code><\/pre>\n
2.  Qpid Proton Kurulumu:<\/strong><\/p>\n
pip install python-qpid-proton<\/code><\/pre>\n
    Veya eski qpid-messaging<\/code> i\u00e7in:<\/p>\n
pip install qpid-messaging<\/code><\/pre>\n
Apache Qpid Y\u00f6netimi ve Yap\u0131land\u0131rmas\u0131<\/h2>\n
Qpid’i kurduktan sonra, onu ihtiya\u00e7lar\u0131n\u0131za g\u00f6re yap\u0131land\u0131rmak ve etkili bir \u015fekilde y\u00f6netmek b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. Bu b\u00f6l\u00fcm, broker’\u0131n temel y\u00f6netim g\u00f6revlerini ve yap\u0131land\u0131rma se\u00e7eneklerini ele almaktad\u0131r.<\/p>\n
Servis Y\u00f6netimi<\/h3>\n
Qpid broker, bir sistem servisi olarak \u00e7al\u0131\u015f\u0131r ve systemd<\/code> veya init.d<\/code> gibi ara\u00e7larla y\u00f6netilir.
\n*   Servisi Ba\u015flatma:<\/strong><\/p>\n
sudo systemctl start qpid-broker<\/code><\/pre>\n
*   Servisi Durdurma:<\/strong><\/p>\n
sudo systemctl stop qpid-broker<\/code><\/pre>\n
*   Servisi Yeniden Ba\u015flatma:<\/strong><\/p>\n
sudo systemctl restart qpid-broker<\/code><\/pre>\n
*   Servisin Durumunu Kontrol Etme:<\/strong><\/p>\n
sudo systemctl status qpid-broker<\/code><\/pre>\n
*   Sistem Ba\u015flang\u0131c\u0131nda Otomatik \u00c7al\u0131\u015fmas\u0131n\u0131 Etkinle\u015ftirme\/Devre D\u0131\u015f\u0131 B\u0131rakma:<\/strong><\/p>\n
sudo systemctl enable qpid-broker\n    sudo systemctl disable qpid-broker<\/code><\/pre>\n
Yap\u0131land\u0131rma Dosyalar\u0131<\/h3>\n
Qpid C++ broker’\u0131n ana yap\u0131land\u0131rma dosyas\u0131 genellikle \/etc\/qpid\/qpid.conf<\/code> veya \/etc\/qpid-broker.conf<\/code> konumunda bulunur. Bu dosya, broker’\u0131n \u00e7al\u0131\u015fma \u015feklini belirleyen \u00e7e\u015fitli parametreleri i\u00e7erir.<\/p>\n
\u00d6nemli yap\u0131land\u0131rma parametreleri:
\n*   port<\/code>:<\/strong> Broker’\u0131n dinleyece\u011fi port (varsay\u0131lan: 5672).
\n*   ssl-port<\/code>:<\/strong> TLS\/SSL \u00fczerinden dinlenecek port (varsay\u0131lan: 5671).
\n*   data-dir<\/code>:<\/strong> Kal\u0131c\u0131 mesajlar\u0131n ve broker verilerinin depolanaca\u011f\u0131 dizin.
\n*   auth<\/code>:<\/strong> Kimlik do\u011frulaman\u0131n etkin olup olmad\u0131\u011f\u0131.
\n*   auth-mechanisms<\/code>:<\/strong> Kullan\u0131lacak SASL kimlik do\u011frulama mekanizmalar\u0131 (PLAIN, ANONYMOUS, EXTERNAL vb.).
\n*   sasl-config-dir<\/code>:<\/strong> SASL yap\u0131land\u0131rma dosyalar\u0131n\u0131n bulundu\u011fu dizin.
\n*   log-enable<\/code>:<\/strong> Hangi bile\u015fenlerin loglama yapaca\u011f\u0131n\u0131 ve log seviyelerini belirler.<\/p>\n
Yap\u0131land\u0131rma dosyas\u0131nda yap\u0131lan de\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in broker’\u0131n yeniden ba\u015flat\u0131lmas\u0131 gerekir.<\/p>\n
Kullan\u0131c\u0131 ve Kimlik Do\u011frulama Y\u00f6netimi<\/h3>\n
Qpid, SASL kullanarak kullan\u0131c\u0131 kimlik do\u011frulamay\u0131 y\u00f6netir. saslpasswd2<\/code> arac\u0131 genellikle kullan\u0131c\u0131lar\u0131 olu\u015fturmak ve parolalar\u0131n\u0131 ayarlamak i\u00e7in kullan\u0131l\u0131r.<\/p>\n
1.  Kullan\u0131c\u0131 Olu\u015fturma:<\/strong>
\n    qpid<\/code> uygulamas\u0131 i\u00e7in bir kullan\u0131c\u0131 olu\u015fturun. qpid<\/code> burada servis ad\u0131d\u0131r.<\/p>\n
sudo saslpasswd2 -a qpid -c \n    # \u00d6rnek: sudo saslpasswd2 -a qpid -c admin<\/code><\/pre>\n
    Parola girmeniz istenecektir.
\n2.  Kullan\u0131c\u0131lar\u0131 Listeleme:<\/strong><\/p>\n
sudo sasldblistusers2 -f \/etc\/sasldb2<\/code><\/pre>\n
3.  Yap\u0131land\u0131rma Dosyas\u0131nda Kimlik Do\u011frulamay\u0131 Etkinle\u015ftirme:<\/strong>
\n    qpid.conf<\/code> dosyas\u0131nda auth=yes<\/code> ve uygun auth-mechanisms<\/code> ayarlar\u0131n\u0131 yap\u0131n. Genellikle auth-mechanisms=PLAIN<\/code> kullan\u0131l\u0131r.<\/p>\n
# \/etc\/qpid\/qpid.conf i\u00e7inde\n    auth=yes\n    auth-mechanisms=PLAIN<\/code><\/pre>\n
    Broker’\u0131 yeniden ba\u015flat\u0131n.<\/p>\n
Sanal Host Y\u00f6netimi<\/h3>\n
Sanal host’lar, ayn\u0131 Qpid broker \u00fczerinde birden fazla izole mesajla\u015fma ortam\u0131 olu\u015fturman\u0131z\u0131 sa\u011flar. Bu, farkl\u0131 uygulamalar\u0131n veya kirac\u0131lar\u0131n mesajla\u015fma kaynaklar\u0131n\u0131 ay\u0131rmak i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n
qpid-config<\/code> arac\u0131 ile sanal host’lar\u0131 y\u00f6netebilirsiniz:
\n*   Sanal Host Olu\u015fturma:<\/strong><\/p>\n
qpid-config add virtualhost my_vhost<\/code><\/pre>\n
*   Sanal Host Listeleme:<\/strong><\/p>\n
qpid-config list virtualhost<\/code><\/pre>\n
*   Sanal Host Silme:<\/strong><\/p>\n
qpid-config del virtualhost my_vhost<\/code><\/pre>\n
Queue ve Exchange Y\u00f6netimi<\/h3>\n
Kuyruklar ve exchange’ler, Qpid’in temel mesaj y\u00f6nlendirme bile\u015fenleridir. Bunlar\u0131 qpid-config<\/code> arac\u0131yla veya istemci API’leri arac\u0131l\u0131\u011f\u0131yla y\u00f6netebilirsiniz.<\/p>\n
*   Kuyruk Olu\u015fturma:<\/strong><\/p>\n
qpid-config add queue my_queue --virtualhost my_vhost<\/code><\/pre>\n
*   Kuyruk Listeleme:<\/strong><\/p>\n
qpid-config list queue --virtualhost my_vhost<\/code><\/pre>\n
*   Exchange Olu\u015fturma (Tipik olarak istemciler taraf\u0131ndan olu\u015fturulur veya varsay\u0131lanlar kullan\u0131l\u0131r):<\/strong><\/p>\n
qpid-config add exchange my_direct_exchange direct --virtualhost my_vhost<\/code><\/pre>\n
*   Binding Olu\u015fturma:<\/strong><\/p>\n
qpid-config add binding my_direct_exchange my_queue my_routing_key --virtualhost my_vhost<\/code><\/pre>\n
    Bu komut, my_direct_exchange<\/code> ile my_queue<\/code> aras\u0131nda my_routing_key<\/code> ile bir ba\u011flama olu\u015fturur. my_direct_exchange<\/code>‘e my_routing_key<\/code> ile gelen mesajlar my_queue<\/code>‘ya y\u00f6nlendirilecektir.<\/p>\n
Mesaj Kal\u0131c\u0131l\u0131\u011f\u0131 (Persistence)<\/h3>\n
Mesaj kal\u0131c\u0131l\u0131\u011f\u0131, broker yeniden ba\u015flat\u0131lsa bile mesajlar\u0131n kaybolmamas\u0131n\u0131 sa\u011flar. Qpid C++ broker, varsay\u0131lan olarak bir dosya tabanl\u0131 depolama mekanizmas\u0131 kullan\u0131r.
\n*   Yap\u0131land\u0131rma:<\/strong> Kal\u0131c\u0131l\u0131k genellikle qpid.conf<\/code> dosyas\u0131ndaki data-dir<\/code> parametresi ile yap\u0131land\u0131r\u0131l\u0131r. Bu dizin, broker’\u0131n kal\u0131c\u0131 verilerini saklayaca\u011f\u0131 yerdir.
\n*   Kal\u0131c\u0131 Kuyruklar:<\/strong> Kuyruklar\u0131 olu\u015ftururken durable=True<\/code> se\u00e7ene\u011fini belirtmek, o kuyru\u011fun ve i\u00e7indeki mesajlar\u0131n kal\u0131c\u0131 olmas\u0131n\u0131 sa\u011flar.<\/p>\n
G\u00fcvenlik<\/h3>\n
Qpid’in g\u00fcvenli\u011fi, kimlik do\u011frulama, yetkilendirme ve \u015fifreleme ile sa\u011flan\u0131r.
\n*   SSL\/TLS:<\/strong> Broker ile istemciler aras\u0131ndaki ileti\u015fimi \u015fifrelemek i\u00e7in SSL\/TLS kullan\u0131labilir. qpid.conf<\/code> dosyas\u0131nda ssl-port<\/code>, ssl-cert-file<\/code>, ssl-key-file<\/code> ve ssl-trust-file<\/code> gibi parametreler yap\u0131land\u0131r\u0131larak etkinle\u015ftirilir. Bir sertifika yetkilisinden al\u0131nm\u0131\u015f veya kendi kendine imzalanm\u0131\u015f sertifikalar kullan\u0131labilir.
\n*   Yetkilendirme (ACL):<\/strong> Qpid, ACL’ler arac\u0131l\u0131\u011f\u0131yla kullan\u0131c\u0131lar\u0131n hangi sanal host’lara, kuyruklara veya exchange’lere eri\u015febilece\u011fini ve hangi i\u015flemleri (g\u00f6nderme, alma, y\u00f6netme) yapabilece\u011fini kontrol etmenizi sa\u011flar. ACL kurallar\u0131, genellikle \/etc\/qpid\/qpid.acl<\/code> gibi bir dosyada tan\u0131mlan\u0131r.
\n    \u00d6rnek ACL kural\u0131:<\/p>\n
ACL ALLOW admin ALL\n    ACL ALLOW guest ACCESS CREATE DELETE PUBLISH CONSUME ON ALL<\/code><\/pre>\n
    Bu \u00f6rnek, admin<\/code> kullan\u0131c\u0131s\u0131na t\u00fcm i\u015flemlere izin verirken, guest<\/code> kullan\u0131c\u0131s\u0131na t\u00fcm kaynaklar \u00fczerinde olu\u015fturma, silme, yay\u0131nlama ve t\u00fcketme izinleri verir.<\/p>\n
\u0130zleme ve Loglama<\/h3>\n
Qpid’in d\u00fczg\u00fcn \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve performans\u0131n\u0131 izlemek \u00f6nemlidir.
\n*   Log Dosyalar\u0131:<\/strong> Qpid broker, \u00e7al\u0131\u015fma zaman\u0131 bilgilerini, uyar\u0131lar\u0131 ve hatalar\u0131 log dosyalar\u0131na yazar. Bu dosyalar\u0131n konumu i\u015fletim sistemine g\u00f6re de\u011fi\u015febilir (\u00f6rne\u011fin, \/var\/log\/qpid\/qpid.log<\/code>). qpid.conf<\/code> dosyas\u0131nda log-enable<\/code> parametresi ile log seviyeleri (debug, info, warning, error) ve loglanan bile\u015fenler ayarlanabilir.
\n*   JMX (Java Broker \u0130\u00e7in):<\/strong> Qpid Java broker, JMX (Java Management Extensions) arac\u0131l\u0131\u011f\u0131yla izlenebilir. Bu, JConsole veya VisualVM gibi ara\u00e7larla broker’\u0131n durumunu, kuyruk istatistiklerini ve ba\u011flant\u0131lar\u0131 ger\u00e7ek zamanl\u0131 olarak g\u00f6rmenizi sa\u011flar.
\n*   Prometheus\/Grafana Entegrasyonu:<\/strong> Daha geli\u015fmi\u015f izleme i\u00e7in, Qpid metrikleri bir Prometheus exporter arac\u0131l\u0131\u011f\u0131yla toplanabilir ve Grafana gibi bir ara\u00e7la g\u00f6rselle\u015ftirilebilir. Bu, broker’\u0131n performans\u0131n\u0131 ve sa\u011fl\u0131\u011f\u0131n\u0131 detayl\u0131 bir \u015fekilde takip etmek i\u00e7in g\u00fc\u00e7l\u00fc bir \u00e7\u00f6z\u00fcm sunar.<\/p>\n
Apache Qpid Kullan\u0131m\u0131: Temel Senaryolar<\/h2>\n
Qpid broker’\u0131 kurup yap\u0131land\u0131rd\u0131ktan sonra, istemci uygulamalar\u0131yla mesaj g\u00f6nderip almaya ba\u015flayabiliriz. A\u015fa\u011f\u0131da Python kullanarak temel \u00fcretici ve t\u00fcketici \u00f6rnekleri verilmi\u015ftir. Bu \u00f6rnekler, qpid-proton<\/code> k\u00fct\u00fcphanesini kullanmaktad\u0131r.<\/p>\n
Mesaj G\u00f6nderme (Producer)<\/h3>\n
Bir \u00fcretici (producer) uygulamas\u0131, broker’a mesaj g\u00f6nderir.<\/p>\n
# producer.py\nfrom proton import Messenger\nimport sys\n\ndef send_message(broker_url, address, message_body):\n    messenger = Messenger()\n    messenger.start()\n\n    message = messenger.message()\n    message.address = address\n    message.body = message_body\n\n    messenger.put(message)\n    messenger.send()\n\n    print(f\"'{message_body}' mesaj\u0131 '{address}' adresine g\u00f6nderildi.\")\n    messenger.stop()\n\nif __name__ == \"__main__\":\n    if len(sys.argv) < 4:\n        print(\"Kullan\u0131m: python producer.py   \")\n        print(\"\u00d6rnek: python producer.py amqp:\/\/localhost:5672 my_queue 'Merhaba Qpid!'\")\n        sys.exit(1)\n\n    broker_url = sys.argv[1] # \u00f6rn: amqp:\/\/localhost:5672\n    address = sys.argv[2]    # \u00f6rn: my_queue veya my_exchange\/my_routing_key\n    message_body = sys.argv[3]\n\n    send_message(broker_url, address, message_body)<\/code><\/pre>\n
Bu kodu \u00e7al\u0131\u015ft\u0131r\u0131rken, broker URL’sini, mesaj\u0131n g\u00f6nderilece\u011fi adresi (kuyruk veya exchange\/routing_key kombinasyonu) ve mesaj i\u00e7eri\u011fini arg\u00fcman olarak vermeniz gerekir.<\/p>\n
python producer.py amqp:\/\/localhost:5672 my_queue \"Bu bir test mesaj\u0131d\u0131r.\"<\/code><\/pre>\n
Mesaj Alma (Consumer)<\/h3>\n
Bir t\u00fcketici (consumer) uygulamas\u0131, broker’dan mesajlar\u0131 al\u0131r.<\/p>\n
# consumer.py\nfrom proton import Messenger\nimport sys\n\ndef receive_messages(broker_url, address):\n    messenger = Messenger()\n    messenger.start()\n\n    messenger.subscribe(address)\n    print(f\"'{address}' adresinden mesajlar bekleniyor. \u00c7\u0131kmak i\u00e7in Ctrl+C.\")\n\n    try:\n        while True:\n            messenger.recv()\n            while messenger.incoming:\n                message = messenger.get()\n                print(f\"Mesaj al\u0131nd\u0131: {message.body} (adres: {message.address})\")\n                # Mesaj\u0131 i\u015fledikten sonra onaylay\u0131n (acknowledge)\n                # messenger.accept(message) # Otomatik kabul genellikle varsay\u0131land\u0131r\n    except KeyboardInterrupt:\n        print(\"\\n\u00c7\u0131k\u0131\u015f yap\u0131l\u0131yor.\")\n    finally:\n        messenger.stop()\n\nif __name__ == \"__main__\":\n    if len(sys.argv) < 3:\n        print(\"Kullan\u0131m: python consumer.py  \")\n        print(\"\u00d6rnek: python consumer.py amqp:\/\/localhost:5672 my_queue\")\n        sys.exit(1)\n\n    broker_url = sys.argv[1]\n    address = sys.argv[2]\n\n    receive_messages(broker_url, address)<\/code><\/pre>\n
Bu t\u00fcketici kodu, belirtilen adresten (kuyruk veya exchange\/routing_key) mesajlar\u0131 dinler.<\/p>\n
python consumer.py amqp:\/\/localhost:5672 my_queue<\/code><\/pre>\n
Routing Mekanizmalar\u0131<\/h3>\n
Yukar\u0131daki \u00f6rnekler do\u011frudan bir kuyru\u011fa mesaj g\u00f6nderip almaktad\u0131r. Ancak Qpid’in g\u00fcc\u00fc, exchange’ler arac\u0131l\u0131\u011f\u0131yla karma\u015f\u0131k y\u00f6nlendirme senaryolar\u0131n\u0131 desteklemesidir.<\/p>\n
*   Direct Exchange:<\/strong>
\n    Bir direct<\/code> exchange’e ba\u011flan\u0131p belirli bir routing_key<\/code> ile mesaj g\u00f6nderdi\u011finizde, bu routing_key<\/code> ile ayn\u0131 anahtara sahip kuyruklara mesaj y\u00f6nlendirilir.<\/p>\n
# Producer i\u00e7in adres: my_direct_exchange\/my_routing_key\n    # Consumer i\u00e7in adres: my_queue (my_direct_exchange ile my_routing_key \u00fczerinden ba\u011fl\u0131 olmal\u0131)<\/code><\/pre>\n
*   Topic Exchange:<\/strong>
\n    topic<\/code> exchange’ler, .<\/code> ile ayr\u0131lm\u0131\u015f hiyerar\u015fik routing_key<\/code>‘ler kullan\u0131r. Kuyruklar, *<\/code> (tek kelime e\u015fle\u015fmesi) ve #<\/code> (s\u0131f\u0131r veya daha fazla kelime e\u015fle\u015fmesi) wildcard’lar\u0131 ile topic<\/code> exchange’e ba\u011flanabilir.
\n    \u00d6rnek: news.sports.football<\/code>, news.weather<\/code> gibi routing key’ler i\u00e7in, news.#<\/code> veya news.sports.*<\/code> gibi binding key’leri kullan\u0131labilir.<\/p>\n
# Producer i\u00e7in adres: my_topic_exchange\/news.sports.football\n    # Consumer i\u00e7in adres: my_topic_exchange\/news.# (veya my_topic_exchange\/news.sports.*)<\/code><\/pre>\n
*   Fanout Exchange:<\/strong>
\n    Bir fanout<\/code> exchange’e g\u00f6nderilen mesajlar, kendisine ba\u011fl\u0131 t\u00fcm kuyruklara kopyalan\u0131r. routing_key<\/code> bu durumda g\u00f6z ard\u0131 edilir. Bu, bir mesaj\u0131 birden fazla t\u00fcketiciye yay\u0131nlamak (broadcast) i\u00e7in idealdir.<\/p>\n
# Producer i\u00e7in adres: my_fanout_exchange\n    # Consumer'lar i\u00e7in adres: my_fanout_exchange\/kuyruk_ad\u0131 (her consumer kendi kuyru\u011funa ba\u011flan\u0131r)<\/code><\/pre>\n
    Bu senaryolarda, qpid-config<\/code> ile exchange ve binding’leri \u00f6nceden olu\u015fturman\u0131z gerekebilir veya istemci k\u00fct\u00fcphaneleri arac\u0131l\u0131\u011f\u0131yla dinamik olarak olu\u015fturulabilirler.<\/p>\n
Sorun Giderme ve En \u0130yi Uygulamalar<\/h2>\n
Apache Qpid’i y\u00f6netirken kar\u015f\u0131la\u015fabilece\u011finiz yayg\u0131n sorunlar ve performans\u0131 optimize etmek i\u00e7in en iyi uygulamalar a\u015fa\u011f\u0131da \u00f6zetlenmi\u015ftir.<\/p>\n
S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar<\/h3>\n
*   Ba\u011flant\u0131 Sorunlar\u0131:<\/strong>
\n    *   Portlar A\u00e7\u0131k De\u011fil:<\/strong> G\u00fcvenlik duvar\u0131n\u0131n (ufw, firewalld) 5672 (AMQP) ve 5671 (AMQPS) portlar\u0131na izin verdi\u011finden emin olun.
\n    *   Broker \u00c7al\u0131\u015fm\u0131yor:<\/strong> sudo systemctl status qpid-broker<\/code> komutuyla broker servisinin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edin.
\n    *   Yanl\u0131\u015f Broker URL’si:<\/strong> \u0130stemci kodunuzdaki broker URL’sinin (\u00f6rne\u011fin amqp:\/\/localhost:5672<\/code>) do\u011fru oldu\u011fundan emin olun.
\n*   Kimlik Do\u011frulama Hatalar\u0131:<\/strong>
\n    *   Yanl\u0131\u015f Kullan\u0131c\u0131 Ad\u0131\/Parola:<\/strong> saslpasswd2<\/code> ile olu\u015fturdu\u011funuz kullan\u0131c\u0131 ad\u0131 ve parolan\u0131n do\u011fru oldu\u011fundan emin olun.
\n    *   SASL Yap\u0131land\u0131rma Sorunlar\u0131:<\/strong> qpid.conf<\/code> dosyas\u0131nda auth=yes<\/code> ve auth-mechanisms=PLAIN<\/code> (veya kulland\u0131\u011f\u0131n\u0131z mekanizma) ayarlar\u0131n\u0131n yap\u0131ld\u0131\u011f\u0131n\u0131 kontrol edin.
\n    *   ACL \u0130zinleri:<\/strong> Kullan\u0131c\u0131n\u0131n istenen i\u015flem i\u00e7in (mesaj g\u00f6nderme\/alma) gerekli yetkilere sahip oldu\u011fundan emin olun (\/etc\/qpid\/qpid.acl<\/code>).
\n*   Mesaj Kayb\u0131 veya \u0130\u015flenmeme:<\/strong>
\n    *   Kal\u0131c\u0131l\u0131k (Persistence):<\/strong> Kal\u0131c\u0131 mesajlar i\u00e7in kuyru\u011fun durable<\/code> olarak ayarland\u0131\u011f\u0131ndan ve broker’\u0131n data-dir<\/code> yap\u0131land\u0131rmas\u0131n\u0131n do\u011fru oldu\u011fundan emin olun.
\n    *   Mesaj Onaylama (Acknowledgement):<\/strong> T\u00fcketicinin mesajlar\u0131 do\u011fru \u015fekilde onaylad\u0131\u011f\u0131ndan (acknowledge) emin olun. Onaylanmayan mesajlar, istemci ba\u011flant\u0131s\u0131 kesildi\u011finde tekrar kuyru\u011fa d\u00f6nebilir veya kaybolabilir (istemci yap\u0131land\u0131rmas\u0131na ba\u011fl\u0131 olarak).
\n    *   Kuyruk Dolulu\u011fu:<\/strong> Kuyru\u011fun maksimum boyutuna ula\u015f\u0131p ula\u015fmad\u0131\u011f\u0131n\u0131 kontrol edin. Dolu kuyruklar yeni mesajlar\u0131 reddedebilir.
\n*   Performans Sorunlar\u0131:<\/strong>
\n    *   Disk G\/\u00c7:<\/strong> Kal\u0131c\u0131 mesajla\u015fma kullan\u0131l\u0131yorsa, disk G\/\u00c7 performans\u0131 darbo\u011faz olabilir. Daha h\u0131zl\u0131 diskler (SSD) kullanmay\u0131 veya disk performans\u0131n\u0131 izlemeyi d\u00fc\u015f\u00fcn\u00fcn.
\n    *   CPU\/Bellek Kullan\u0131m\u0131:<\/strong> Broker’\u0131n CPU ve bellek kullan\u0131m\u0131n\u0131 izleyin. Y\u00fcksek kullan\u0131m, daha fazla kayna\u011fa ihtiya\u00e7 duyuldu\u011funu veya optimizasyon gerekti\u011fini g\u00f6sterebilir.
\n    *   A\u011f Gecikmesi:<\/strong> Broker ile istemciler aras\u0131ndaki a\u011f gecikmesi, mesajla\u015fma performans\u0131n\u0131 etkileyebilir.<\/p>\n
Performans \u0130pu\u00e7lar\u0131<\/h3>\n
*   Mesaj Boyutunu Optimize Edin:<\/strong> M\u00fcmk\u00fcn oldu\u011funca k\u00fc\u00e7\u00fck ve verimli mesajlar kullan\u0131n. B\u00fcy\u00fck mesajlar a\u011f ve broker \u00fczerindeki y\u00fck\u00fc art\u0131r\u0131r.
\n*   Toplu \u0130\u015flem (Batching):<\/strong> Tek tek mesaj g\u00f6ndermek yerine, birden fazla mesaj\u0131 tek bir i\u015flemde g\u00f6ndererek a\u011f gecikmesini ve broker \u00fczerindeki y\u00fck\u00fc azaltabilirsiniz.
\n*   \u00d6n Getirme (Prefetch):<\/strong> T\u00fcketiciler, bir seferde birden fazla mesaj\u0131 \u00f6nceden getirerek (prefetch) performanslar\u0131n\u0131 art\u0131rabilir. Bu, broker’dan s\u00fcrekli tek tek mesaj isteme overhead’ini azalt\u0131r.
\n*   Kal\u0131c\u0131 ve Ge\u00e7ici Mesajlar:<\/strong> Yaln\u0131zca kritik mesajlar i\u00e7in kal\u0131c\u0131l\u0131\u011f\u0131 kullan\u0131n. Ge\u00e7ici (transient) mesajlar daha h\u0131zl\u0131 i\u015flenir \u00e7\u00fcnk\u00fc diske yaz\u0131lmazlar.
\n*   Do\u011fru Exchange T\u00fcr\u00fcn\u00fc Se\u00e7in:<\/strong> \u0130htiya\u00e7lar\u0131n\u0131za en uygun exchange t\u00fcr\u00fcn\u00fc kullan\u0131n. \u00d6rne\u011fin, basit birebir ileti\u015fim i\u00e7in direct<\/code> exchange yeterlidir, ancak yay\u0131nlama i\u00e7in fanout<\/code> daha uygundur.
\n*   Sanal Hostlar\u0131 Kullan\u0131n:<\/strong> Farkl\u0131 uygulamalar i\u00e7in sanal host’lar kullanarak kaynak izolasyonu sa\u011flay\u0131n ve broker’\u0131n y\u00fck\u00fcn\u00fc mant\u0131ksal olarak da\u011f\u0131t\u0131n.<\/p>\n
Y\u00fcksek Eri\u015filebilirlik (HA) ve \u00d6l\u00e7eklenebilirlik<\/h3>\n
Apache Qpid, y\u00fcksek eri\u015filebilirlik ve \u00f6l\u00e7eklenebilirlik i\u00e7in \u00e7e\u015fitli mekanizmalar sunar:
\n*   Broker Clustering:<\/strong> Birden fazla Qpid broker’\u0131n\u0131 bir araya getirerek y\u00fcksek eri\u015filebilirlik ve y\u00fck dengeleme sa\u011flayabilirsiniz. Bu sayede bir broker \u00e7\u00f6kerse, di\u011ferleri hizmet vermeye devam edebilir. Qpid C++ broker, qpid-ha<\/code> eklentisi ile bu \u00f6zelli\u011fi destekler.
\n*   Federasyon:<\/strong> Farkl\u0131 co\u011frafi konumlardaki broker’lar aras\u0131nda mesajlar\u0131 senkronize etmek i\u00e7in federasyon kullan\u0131labilir. Bu, da\u011f\u0131t\u0131k sistemlerde mesajla\u015fma i\u00e7in idealdir.
\n*   Mesaj Replikasyonu:<\/strong> Kal\u0131c\u0131 mesajlar\u0131n birden fazla broker aras\u0131nda replike edilmesi, veri kayb\u0131 riskini azalt\u0131r.<\/p>\n
G\u00fcvenlik \u0130pu\u00e7lar\u0131<\/h3>\n
*   SSL\/TLS Kullan\u0131n:<\/strong> \u00dcretim ortamlar\u0131nda her zaman SSL\/TLS kullanarak broker ile istemciler aras\u0131ndaki ileti\u015fimi \u015fifreleyin.
\n*   G\u00fc\u00e7l\u00fc Kimlik Do\u011frulama:<\/strong> PLAIN<\/code> yerine daha g\u00fc\u00e7l\u00fc SASL mekanizmalar\u0131 (\u00f6rne\u011fin SCRAM-SHA-256<\/code>) kullanmay\u0131 d\u00fc\u015f\u00fcn\u00fcn.
\n*   Detayl\u0131 Yetkilendirme (ACL):<\/strong> Her kullan\u0131c\u0131ya veya uygulama hesab\u0131na yaln\u0131zca ihtiya\u00e7 duydu\u011fu minimum yetkileri veren ACL kurallar\u0131 tan\u0131mlay\u0131n (Least Privilege Prensibi).
\n*   Varsay\u0131lan Kullan\u0131c\u0131lar\u0131 Kald\u0131r\u0131n\/Devre D\u0131\u015f\u0131 B\u0131rak\u0131n:<\/strong> Kurulumdan sonra varsay\u0131lan olarak gelen guest<\/code> gibi kullan\u0131c\u0131lar\u0131 devre d\u0131\u015f\u0131 b\u0131rak\u0131n veya kald\u0131r\u0131n.
\n*   A\u011f Segmentasyonu:<\/strong> Qpid broker’\u0131 di\u011fer hassas sistemlerden izole edilmi\u015f bir a\u011f segmentine yerle\u015ftirin.<\/p>\n
Dok\u00fcmantasyon ve Topluluk Kaynaklar\u0131<\/h3>\n
Kar\u015f\u0131la\u015fabilece\u011finiz sorunlar veya ileri d\u00fczey konular i\u00e7in Apache Qpid’in resmi dok\u00fcmantasyonu (qpid.apache.org) en iyi kaynakt\u0131r. Ayr\u0131ca, Qpid kullan\u0131c\u0131 ve geli\u015ftirici posta listeleri, aktif bir topluluk deste\u011fi sunar.<\/p>\n
Sonu\u00e7<\/h2>\n
Apache Qpid, AMQP standard\u0131n\u0131 uygulayan g\u00fc\u00e7l\u00fc, esnek ve g\u00fcvenilir bir mesaj arac\u0131s\u0131d\u0131r. Da\u011f\u0131t\u0131k sistemlerde ve mikroservis mimarilerinde asenkron ileti\u015fimi y\u00f6netmek i\u00e7in kritik bir rol oynar. Bu makalede, Qpid’in temel mimari bile\u015fenlerinden ba\u015flayarak, farkl\u0131 Linux da\u011f\u0131t\u0131mlar\u0131 \u00fczerinde kurulum ad\u0131mlar\u0131na, detayl\u0131 y\u00f6netim ve yap\u0131land\u0131rma pratiklerine kadar kapsaml\u0131 bir rehber sunulmu\u015ftur. Kullan\u0131c\u0131 ve g\u00fcvenlik y\u00f6netimi, kal\u0131c\u0131l\u0131k ayarlar\u0131 ve izleme gibi \u00f6nemli konular ele al\u0131nm\u0131\u015f, ayr\u0131ca Python ile temel \u00fcretici ve t\u00fcketici \u00f6rnekleri ile pratik kullan\u0131m senaryolar\u0131 g\u00f6sterilmi\u015ftir.<\/p>\n
Qpid’in sundu\u011fu esneklik ve performans, onu finans, telekom\u00fcnikasyon ve IoT gibi sekt\u00f6rlerdeki zorlu mesajla\u015fma ihtiya\u00e7lar\u0131 i\u00e7in ideal bir \u00e7\u00f6z\u00fcm haline getirmektedir. Do\u011fru kurulum, yap\u0131land\u0131rma ve y\u00f6netim pratikleriyle, Apache Qpid sistemlerinizin ileti\u015fim omurgas\u0131n\u0131 g\u00fcvenilir bir \u015fekilde olu\u015fturabilir ve \u00f6l\u00e7eklenebilirli\u011fini art\u0131rabilirsiniz. Unutulmamal\u0131d\u0131r ki, her sistem gibi Qpid’in de etkin bir \u015fekilde \u00e7al\u0131\u015fmas\u0131 i\u00e7in d\u00fczenli izleme, bak\u0131m ve g\u00fcvenlik g\u00fcncellemeleri hayati \u00f6nem ta\u015f\u0131maktad\u0131r.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Apache Qpid Kurulumu ve Y\u00f6netimi\nGiri\u015f\nG\u00fcn\u00fcm\u00fcz\u00fcn modern uygulama mimarilerinde, mikroservisler ve da\u011f\u0131t\u0131k sistemler giderek daha fazla \u00f6nem","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":[874],"tags":[],"class_list":{"0":"post-31589","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-server","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nApache Qpid Kurulumu ve Y\u00f6netimi - 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\/apache-qpid-kurulumu-ve-yonetimi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Apache Qpid Kurulumu ve Y\u00f6netimi\" \/>\n<meta property=\"og:description\" content=\"Apache Qpid Kurulumu ve Y\u00f6netimi Giri\u015f G\u00fcn\u00fcm\u00fcz\u00fcn modern uygulama mimarilerinde, mikroservisler ve da\u011f\u0131t\u0131k sistemler giderek daha fazla \u00f6nem\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-11T13:41:25+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=\"22 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Apache Qpid Kurulumu ve Y\u00f6netimi\",\"datePublished\":\"2025-10-11T13:41:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\"},\"wordCount\":3662,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Server\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\",\"name\":\"Apache Qpid Kurulumu ve Y\u00f6netimi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-11T13:41:25+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Apache Qpid Kurulumu ve Y\u00f6netimi\"}]},{\"@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":"Apache Qpid Kurulumu ve Y\u00f6netimi - 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\/apache-qpid-kurulumu-ve-yonetimi\/","og_locale":"tr_TR","og_type":"article","og_title":"Apache Qpid Kurulumu ve Y\u00f6netimi","og_description":"Apache Qpid Kurulumu ve Y\u00f6netimi Giri\u015f G\u00fcn\u00fcm\u00fcz\u00fcn modern uygulama mimarilerinde, mikroservisler ve da\u011f\u0131t\u0131k sistemler giderek daha fazla \u00f6nem","og_url":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-11T13:41:25+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"22 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Apache Qpid Kurulumu ve Y\u00f6netimi","datePublished":"2025-10-11T13:41:25+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/"},"wordCount":3662,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Server"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/","url":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/","name":"Apache Qpid Kurulumu ve Y\u00f6netimi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-11T13:41:25+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/apache-qpid-kurulumu-ve-yonetimi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Apache Qpid Kurulumu ve Y\u00f6netimi"}]},{"@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\/31589","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=31589"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31589\/revisions"}],"predecessor-version":[{"id":31590,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31589\/revisions\/31590"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=31589"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=31589"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=31589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}