resmi belgelerinden<\/a> kurulum talimatlar\u0131n\u0131 takip edebilirsiniz.<\/li>\n<\/ul>\n\u0130lk ad\u0131m olarak, KEDA’n\u0131n kendisini k\u00fcmenize kurman\u0131z gerekmektedir. KEDA HTTP Add-on, KEDA’n\u0131n bir uzant\u0131s\u0131 oldu\u011fundan, \u00f6nce temel KEDA kurulumu yap\u0131lmal\u0131d\u0131r:<\/p>\n
\n# KEDA Helm deposunu ekle\nhelm repo add keda https:\/\/kedacore.github.io\/charts\n\n# Helm deposunu g\u00fcncelle\nhelm repo update\n\n# KEDA'y\u0131 varsay\u0131lan namespace'e kur (veya istedi\u011finiz ba\u015fka bir namespace'e)\nhelm install keda keda\/keda --namespace keda --create-namespace\n <\/pre>\n<\/code><\/p>\n
Kurulumun ba\u015far\u0131l\u0131 oldu\u011funu do\u011frulamak i\u00e7in KEDA podlar\u0131n\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edebilirsiniz:<\/p>\n
\nkubectl get pods -n keda\n <\/pre>\n<\/code><\/p>\n
\u00c7\u0131kt\u0131da keda-operator-...<\/code> ve keda-admission-webhooks-...<\/code> benzeri podlar\u0131n Running<\/code> durumunda oldu\u011funu g\u00f6rmelisiniz.<\/p>\n2. KEDA HTTP Add-on Kurulumu Nas\u0131l Yap\u0131l\u0131r?<\/h3>\n
KEDA y\u00fcklendikten sonra, HTTP Add-on'u kurabiliriz. Bu eklenti de kendi Helm chart'\u0131na sahiptir:<\/p>\n
\n# KEDA HTTP Add-on Helm deposunu ekle\nhelm repo add keda-http https:\/\/kedacore.github.io\/http-add-on-charts\n\n# Helm deposunu g\u00fcncelle\nhelm repo update\n\n# KEDA HTTP Add-on'u kur\nhelm install keda-http-add-on keda-http\/keda-http-add-on --namespace keda --create-namespace\n <\/pre>\n<\/code><\/p>\n
Kurulumu do\u011frulamak i\u00e7in:<\/p>\n
\nkubectl get pods -n keda\n <\/pre>\n<\/code><\/p>\n
\u015eimdi \u00e7\u0131kt\u0131da keda-http-add-on-...<\/code> ile ba\u015flayan podlar\u0131 da g\u00f6rmelisiniz. Bu podlar, gelen HTTP isteklerini dinleyecek ve metrikleri KEDA'ya iletecek olan proxy'yi ve denetleyiciyi i\u00e7erir.<\/p>\n3. Uygulaman\u0131z\u0131 ve \u00d6l\u00e7eklendirme Kural\u0131n\u0131 Nas\u0131l Yap\u0131land\u0131r\u0131rs\u0131n\u0131z?<\/h3>\n
\u015eimdi s\u0131ra, \u00f6l\u00e7eklendirmek istedi\u011finiz uygulaman\u0131z\u0131 da\u011f\u0131tmaya ve KEDA HTTP Add-on i\u00e7in \u00f6l\u00e7eklendirme kural\u0131n\u0131 tan\u0131mlamaya geldi. \u00d6rnek olarak basit bir Nginx uygulamas\u0131n\u0131 kullanaca\u011f\u0131z.<\/p>\n
a. Uygulama Da\u011f\u0131t\u0131m\u0131 (Deployment ve Service)<\/h4>\n
\u00d6ncelikle, \u00f6rnek uygulamam\u0131z\u0131 Kubernetes k\u00fcmenize da\u011f\u0131tal\u0131m. Bu, uygulaman\u0131z\u0131n kendisi olacakt\u0131r.<\/p>\n
\n# app-deployment.yaml\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: http-echo-app\n labels:\n app: http-echo-app\nspec:\n replicas: 1\n selector:\n matchLabels:\n app: http-echo-app\n template:\n metadata:\n labels:\n app: http-echo-app\n spec:\n containers:\n - name: http-echo\n image: hashicorp\/http-echo:latest\n args:\n - \"-text=Merhaba, KEDA HTTP Add-on D\u00fcnyas\u0131!\"\n ports:\n - containerPort: 5678\n---\napiVersion: v1\nkind: Service\nmetadata:\n name: http-echo-app-service\nspec:\n selector:\n app: http-echo-app\n ports:\n - protocol: TCP\n port: 80\n targetPort: 5678\n <\/pre>\n<\/code><\/p>\n
Bu YAML dosyas\u0131n\u0131 app-deployment.yaml<\/code> olarak kaydedin ve uygulay\u0131n:<\/p>\n\nkubectl apply -f app-deployment.yaml\n <\/pre>\n<\/code><\/p>\n
b. HTTPScaledObject Tan\u0131m\u0131<\/h4>\n
KEDA HTTP Add-on ile \u00f6l\u00e7eklendirme yapmak i\u00e7in HTTPScaledObject<\/code> ad\u0131nda \u00f6zel bir Kaynak (Custom Resource) kullan\u0131r\u0131z. Bu kaynak, hangi uygulaman\u0131n \u00f6l\u00e7eklenece\u011fini ve hangi HTTP metriklerine g\u00f6re \u00f6l\u00e7eklenece\u011fini tan\u0131mlar.<\/p>\n\n# http-scaled-object.yaml\napiVersion: http.keda.sh\/v1alpha1\nkind: HTTPScaledObject\nmetadata:\n name: http-echo-scaledobject\n namespace: default # Uygulaman\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 namespace\nspec:\n host: example.com # Bu, d\u0131\u015far\u0131dan eri\u015filen bir host olabilir veya bir i\u00e7 servis ad\u0131.\n # E\u011fer Ingress kullan\u0131yorsan\u0131z, Ingress host ad\u0131n\u0131zla e\u015fle\u015fmelidir.\n # Test i\u00e7in \"localhost\" veya servisinizin IP'si de olabilir.\n targetService: http-echo-app-service # Uygulaman\u0131z\u0131n servis ad\u0131\n port: 80 # Uygulama servisinin dinledi\u011fi port\n scaleTargetRef:\n deploymentName: http-echo-app # \u00d6l\u00e7eklenecek uygulaman\u0131n Deployment ad\u0131\n containerName: http-echo # \u00d6l\u00e7eklenecek kapsay\u0131c\u0131n\u0131n ad\u0131 (iste\u011fe ba\u011fl\u0131)\n triggers:\n - type: requests # \u0130stek say\u0131s\u0131na g\u00f6re \u00f6l\u00e7eklendirme\n metadata:\n value: \"10\" # Her bir pod i\u00e7in saniyede ortalama 10 istek hedefi\n # queueLength: \"100\" # \u00d6rnek: HTTP kuyru\u011fundaki bekleyen istek say\u0131s\u0131 (alternatif bir tetikleyici)\n cooldownPeriod: 30 # Son iste\u011fin i\u015flenmesinden sonra podlar\u0131n minimum say\u0131s\u0131na d\u00f6nme s\u00fcresi (saniye)\n advanced:\n horizontalPodAutoscalerConfig:\n behavior:\n scaleDown:\n stabilizationWindowSeconds: 60\n policies:\n - type: Percent\n value: 100\n periodSeconds: 15\n scaleUp:\n stabilizationWindowSeconds: 0\n policies:\n - type: Percent\n value: 100\n periodSeconds: 15\n <\/pre>\n<\/code><\/p>\n
Bu YAML dosyas\u0131n\u0131 http-scaled-object.yaml<\/code> olarak kaydedin ve uygulay\u0131n:<\/p>\n\nkubectl apply -f http-scaled-object.yaml\n <\/pre>\n<\/code><\/p>\n
\n
Uzman \u0130pucu:<\/strong> host<\/code> alan\u0131, KEDA HTTP Add-on proxy'sinin hangi ana bilgisayar ad\u0131n\u0131 dinleyece\u011fini belirtir. E\u011fer uygulaman\u0131za bir Ingress Controller arac\u0131l\u0131\u011f\u0131yla eri\u015fiyorsan\u0131z, Ingress kural\u0131n\u0131zdaki host ad\u0131yla e\u015fle\u015fmelidir. Yerel testler i\u00e7in bazen localhost<\/code> kullan\u0131labilir, ancak genellikle ger\u00e7ek bir DNS ad\u0131 veya Kubernetes i\u00e7indeki bir servis ad\u0131 olmal\u0131d\u0131r. value: \"10\"<\/code>, her podun saniyede ortalama 10 iste\u011fi i\u015flemesini hedefler. Bu de\u011feri uygulaman\u0131z\u0131n performans\u0131na g\u00f6re ayarlaman\u0131z kritik \u00f6neme sahiptir.\n <\/div>\nKEDA ve HPA art\u0131k otomatik olarak http-echo-app<\/code> uygulaman\u0131z\u0131n pod say\u0131s\u0131n\u0131, gelen HTTP isteklerinin hacmine g\u00f6re y\u00f6netecektir. Ba\u015flang\u0131\u00e7ta 1 podunuz olacak. \u0130stek g\u00f6ndermeye ba\u015flad\u0131\u011f\u0131n\u0131zda, istek say\u0131s\u0131 10\/saniyeyi a\u015ft\u0131\u011f\u0131nda KEDA, daha fazla pod olu\u015fturarak y\u00fck\u00fc dengeleyecektir.<\/p>\n4. \u00d6l\u00e7eklendirmeyi Test Etme<\/h3>\n
Uygulaman\u0131z\u0131n nas\u0131l \u00f6l\u00e7eklendi\u011fini g\u00f6rmek i\u00e7in bir y\u00fck testi arac\u0131 kullanabilirsiniz. \u00d6rne\u011fin, hey<\/code> veya ab<\/code> (ApacheBench) gibi ara\u00e7lar i\u015finizi g\u00f6recektir.<\/p>\n\u00d6ncelikle, KEDA HTTP Add-on'un d\u0131\u015far\u0131dan eri\u015filebilir bir IP'ye veya host'a sahip oldu\u011fundan emin olun. Genellikle, HTTP Add-on bir LoadBalancer tipi servis ile gelir veya Ingress Controller ile entegre edilir. Test amac\u0131yla, KEDA HTTP Add-on'un servisini port-forwarding ile yerel makinenize y\u00f6nlendirebilirsiniz:<\/p>\n
\n# KEDA HTTP Add-on servisinin ad\u0131n\u0131 ve portunu bulun\nkubectl get svc -n keda\n\n# \u00d6rne\u011fin, servisin ad\u0131 keda-http-add-on-interceptor-proxy<\/code> ve portu 8080 ise\nkubectl port-forward svc\/keda-http-add-on-interceptor-proxy 8080:8080 -n keda\n <\/pre>\n<\/code><\/p>\n
\u015eimdi yeni bir terminal a\u00e7\u0131n ve y\u00fck g\u00f6ndermeye ba\u015flay\u0131n. hey<\/code> arac\u0131n\u0131 kullanarak saniyede 50 istek g\u00f6nderelim:<\/p>\n\nhey -n 10000 -c 50 -q 50 http:\/\/localhost:8080\/\n <\/pre>\n<\/code><\/p>\n
Bu komut, 10000 istek g\u00f6nderir, ayn\u0131 anda 50 ba\u011flant\u0131 a\u00e7ar ve saniyede 50 sorgu yapmaya \u00e7al\u0131\u015f\u0131r. Kubernetes k\u00fcmenizde podlar\u0131n \u00f6l\u00e7eklendi\u011fini g\u00f6zlemleyebilirsiniz:<\/p>\n
\nkubectl get deployment http-echo-app -w # \"-w\" bayra\u011f\u0131 de\u011fi\u015fiklikleri izler\n <\/pre>\n<\/code><\/p>\n
Pod say\u0131s\u0131n\u0131n artt\u0131\u011f\u0131n\u0131 ve y\u00fck testi bittikten sonra yava\u015f\u00e7a azald\u0131\u011f\u0131n\u0131 g\u00f6receksiniz. Bu, KEDA HTTP Add-on'un ba\u015far\u0131l\u0131 bir \u015fekilde \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/p>\n
\n
KEDA HTTP Add-on \u0130zleme Panosu i\u00e7in Mobil Uyumlu HTML \u00d6rne\u011fi<\/h3>\n
Makalenin genel mobil uyumlulu\u011fu i\u00e7in, KEDA ile ilgili bir izleme panosunun veya bir uygulaman\u0131n durum sayfas\u0131n\u0131n mobil cihazlarda nas\u0131l daha iyi g\u00f6r\u00fcnebilece\u011fine dair basit bir CSS medya sorgusu \u00f6rne\u011fi ekleyelim. Bu, KEDA metriklerini veya uygulama sa\u011fl\u0131\u011f\u0131n\u0131 g\u00f6steren bir aray\u00fcz i\u00e7in ge\u00e7erli olabilir.<\/p>\n
\n\n\n\n \n \n KEDA Durum Panosu<\/title>\n <style>\n body { font-family: Arial, sans-serif; margin: 20px; }\n .container {\n display: grid;\n grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));\n gap: 20px;\n }\n .card {\n background-color: #f4f4f4;\n border: 1px solid #ddd;\n padding: 15px;\n border-radius: 8px;\n box-shadow: 0 2px 4px rgba(0,0,0,0.1);\n }\n h3 { color: #333; }\n .status { font-weight: bold; }\n .status.green { color: green; }\n .status.red { color: red; }\n\n \/* Mobil Cihazlar \u0130\u00e7in Medya Sorgusu *\/\n @media (max-width: 768px) {\n .container {\n grid-template-columns: 1fr; \/* K\u00fc\u00e7\u00fck ekranlarda tek s\u00fctun *\/\n }\n .card {\n margin-bottom: 10px;\n }\n }\n <\/style>\n<\/head>\n<body>\n <h1>KEDA Durum Panosu<\/h1>\n <div class=\"container\">\n <div class=\"card\">\n <h3>Uygulama: HTTP Echo<\/h3>\n <p>Mevcut Pod Say\u0131s\u0131: <span class=\"status green\">3<\/span><\/p>\n <p>Ortalama \u0130stek\/Sn: 25<\/p>\n <\/div>\n <div class=\"card\">\n <h3>KEDA HTTP Add-on<\/h3>\n <p>Durum: <span class=\"status green\">\u00c7al\u0131\u015f\u0131yor<\/span><\/p>\n <p>Toplam \u0130zlenen Host: 1<\/p>\n <\/div>\n <\/div>\n<\/body>\n<\/html>\n <\/pre>\n<p><\/code><\/p>\n<p>Yukar\u0131daki \u00f6rnek, basit bir durum panosunun nas\u0131l duyarl\u0131 hale getirilebilece\u011fini g\u00f6stermektedir. 768 pikselden k\u00fc\u00e7\u00fck ekranlarda, kartlar tek s\u00fctun halinde listelenerek mobil okunabilirli\u011fi art\u0131r\u0131l\u0131r. Bu t\u00fcr yakla\u015f\u0131mlar, Kubernetes ve KEDA y\u00f6netim aray\u00fczlerinin de mobil cihazlarda daha kullan\u0131\u015fl\u0131 olmas\u0131n\u0131 sa\u011flar.<\/p>\n<\/p><\/div>\n<h2>Ger\u00e7ek D\u00fcnya Senaryolar\u0131: Hangi Durumlarda KEDA HTTP Add-on Kullanmal\u0131y\u0131z?<\/h2>\n<p>KEDA HTTP Add-on'un sadece teorik bir konsept olmad\u0131\u011f\u0131n\u0131, aksine bir\u00e7ok ger\u00e7ek d\u00fcnya uygulamas\u0131nda kritik problemlerin \u00e7\u00f6z\u00fcm\u00fcne yard\u0131mc\u0131 oldu\u011funu vaka analizleri ile g\u00f6rebiliriz. Dinamik istek hacmi y\u00f6netimi, \u00f6zellikle belirli end\u00fcstriler ve uygulama t\u00fcrleri i\u00e7in vazge\u00e7ilmezdir. \u0130\u015fte KEDA HTTP Add-on'un parlad\u0131\u011f\u0131 baz\u0131 senaryolar:<\/p>\n<h3>1. E-ticaret Siteleri ve Fla\u015f Kampanyalar<\/h3>\n<p><strong>Vaka Analizi: B\u00fcy\u00fck Bir E-ticaret Platformu<\/strong><\/p>\n<p>Hayal edin ki, bir e-ticaret \u015firketi olan \"TrendSepet\", her y\u0131l Kara Cuma (Black Friday) ve Cyber Pazartesi gibi b\u00fcy\u00fck indirim g\u00fcnlerinde, normal trafik hacminin 10 ila 50 kat\u0131na kadar ani bir art\u0131\u015f ya\u015f\u0131yor. Geleneksel olarak, bu d\u00f6nemlerde IT ekibi haftalar \u00f6ncesinden sunucu kapasitesini manuel olarak art\u0131r\u0131r (over-provisioning) ve indirimler bittikten sonra tekrar d\u00fc\u015f\u00fcr\u00fcr. Bu s\u00fcre\u00e7 hem operasyonel y\u00fck olu\u015fturur hem de y\u00fcksek kapasitenin b\u00fcy\u00fck bir k\u0131sm\u0131 bo\u015fta durdu\u011fu i\u00e7in muazzam bulut maliyetleri yarat\u0131r.<\/p>\n<p>TrendSepet, bu sorunu \u00e7\u00f6zmek i\u00e7in Kubernetes'e ge\u00e7meye ve KEDA HTTP Add-on kullanmaya karar verdi. Ana \u00fcr\u00fcn katalog ve \u00f6deme servislerini KEDA HTTP Add-on ile \u00f6l\u00e7eklendirdi. <code>HTTPScaledObject<\/code> tan\u0131mlar\u0131, her podun saniyede ortalama 50 HTTP iste\u011fi hedeflemesini ve kuyruktaki istek say\u0131s\u0131 belirli bir e\u015fi\u011fi a\u015ft\u0131\u011f\u0131nda h\u0131zla \u00f6l\u00e7eklenmesini sa\u011flayacak \u015fekilde ayarland\u0131. Kampanya ba\u015flad\u0131\u011f\u0131nda, saniyeler i\u00e7inde pod say\u0131lar\u0131 1'den 100'e kadar \u00e7\u0131kt\u0131, t\u00fcm istekler sorunsuz bir \u015fekilde i\u015flendi. Kampanya bitti\u011finde ve trafik normale d\u00f6nd\u00fc\u011f\u00fcnde, KEDA pod say\u0131lar\u0131n\u0131 otomatik olarak minimum seviyeye indirdi.<\/p>\n<p><strong>Sonu\u00e7:<\/strong> TrendSepet, KEDA HTTP Add-on sayesinde kampanya d\u00f6nemlerindeki performanstan \u00f6d\u00fcn vermeden, gereksiz kaynak tahsisi nedeniyle olu\u015fan bulut maliyetlerinden %60 oran\u0131nda tasarruf etti. Ayr\u0131ca, IT ekibinin manuel m\u00fcdahale ihtiyac\u0131 ortadan kalkt\u0131\u011f\u0131 i\u00e7in operasyonel y\u00fckleri azald\u0131 ve di\u011fer kritik projelere odaklanabildiler. M\u00fc\u015fteriler ise yo\u011funluktan etkilenmeden h\u0131zl\u0131 bir al\u0131\u015fveri\u015f deneyimi ya\u015fad\u0131.<\/p>\n<h3>2. Mikroservis Tabanl\u0131 API A\u011f Ge\u00e7itleri ve Arka U\u00e7 Servisleri<\/h3>\n<p>Mikroservis mimarilerinde, bir API a\u011f ge\u00e7idi (API Gateway) veya belirli bir mikroservis, di\u011fer servislerden veya d\u0131\u015f sistemlerden gelen binlerce iste\u011fi i\u015fleyebilir. Bu servislerin y\u00fck\u00fc, farkl\u0131 \u00f6n u\u00e7 uygulamalar\u0131ndan veya di\u011fer mikroservislerden gelen taleplere g\u00f6re b\u00fcy\u00fck \u00f6l\u00e7\u00fcde de\u011fi\u015febilir. \u00d6rne\u011fin, bir kimlik do\u011frulama servisi, belirli saatlerde veya kullan\u0131c\u0131 giri\u015finin yo\u011fun oldu\u011fu d\u00f6nemlerde (i\u015f ba\u015flang\u0131c\u0131, \u00f6\u011fle aras\u0131) ani pikler ya\u015fayabilir.<\/p>\n<p>KEDA HTTP Add-on, bu t\u00fcr kritik ve payla\u015f\u0131lan servislerin dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flayarak, t\u00fcm sistemin genel performans\u0131n\u0131 ve yan\u0131t verebilirli\u011fini art\u0131r\u0131r. Gelen istek yo\u011funlu\u011funa g\u00f6re API a\u011f ge\u00e7idi podlar\u0131 veya belirli bir mikroservisin podlar\u0131 art\u0131r\u0131l\u0131r. Bu, di\u011fer servislerin bu servisin yava\u015flamas\u0131 nedeniyle etkilenmesini \u00f6nler ve mimarinin genel direncini art\u0131r\u0131r.<\/p>\n<h3>3. Medya ve Haber Portallar\u0131<\/h3>\n<p>Son dakika haberleri, viral olan i\u00e7erikler veya b\u00fcy\u00fck spor etkinlikleri gibi olaylar, medya ve haber sitelerine anl\u0131k ve \u00f6ng\u00f6r\u00fclemeyen trafik ak\u0131\u015flar\u0131 getirebilir. Geleneksel CDN'ler statik i\u00e7erik i\u00e7in harika olsa da, dinamik i\u00e7erik sunan API'ler ve ki\u015fiselle\u015ftirilmi\u015f i\u00e7erik motorlar\u0131 yine de arka u\u00e7 sunucular\u0131na ihtiya\u00e7 duyar. KEDA HTTP Add-on, bu senaryoda haber sitesinin i\u00e7erik sunum katman\u0131n\u0131 veya API servislerini an\u0131nda \u00f6l\u00e7eklendirerek, milyonlarca kullan\u0131c\u0131n\u0131n ayn\u0131 anda i\u00e7eri\u011fe eri\u015fmesini m\u00fcmk\u00fcn k\u0131lar. Trafik azald\u0131\u011f\u0131nda da kaynaklar\u0131 otomatik olarak geri \u00e7ekerek maliyetleri d\u00fc\u015f\u00fcr\u00fcr.<\/p>\n<h3>4. IoT ve Ger\u00e7ek Zamanl\u0131 Veri \u0130\u015fleme Uygulamalar\u0131<\/h3>\n<p>Nesnelerin \u0130nterneti (IoT) cihazlar\u0131ndan gelen veri ak\u0131\u015flar\u0131 veya ger\u00e7ek zamanl\u0131 analiz platformlar\u0131, bazen \u00f6ng\u00f6r\u00fclemeyen veri hacmi dalgalanmalar\u0131 ya\u015far. Bu platformlar genellikle HTTP veya WebSockets \u00fczerinden veri al\u0131m\u0131 yaparlar. KEDA HTTP Add-on, bu t\u00fcr veri al\u0131m servislerini gelen ba\u011flant\u0131 ve istek say\u0131s\u0131na g\u00f6re \u00f6l\u00e7eklendirerek, herhangi bir veri kayb\u0131 veya gecikme olmadan y\u00fcksek hacimli verinin i\u015flenmesini sa\u011flar. \u00d6rne\u011fin, bir ak\u0131ll\u0131 \u015fehir uygulamas\u0131ndan gelen sens\u00f6r verileri aniden artt\u0131\u011f\u0131nda, KEDA bu verileri i\u015fleyecek podlar\u0131 h\u0131zla devreye alabilir.<\/p>\n<p>\u00d6zetle, KEDA HTTP Add-on, HTTP istek hacminin i\u015f y\u00fck\u00fcn\u00fc do\u011frudan belirledi\u011fi ve bu hacmin zaman i\u00e7inde \u00f6nemli \u00f6l\u00e7\u00fcde dalgaland\u0131\u011f\u0131 her t\u00fcrl\u00fc senaryoda g\u00fc\u00e7l\u00fc bir \u00e7\u00f6z\u00fcmd\u00fcr. Uygulamalar\u0131n\u0131z\u0131n performans\u0131n\u0131 garanti ederken, bulut maliyetlerinizi optimize etmenize ve operasyonel y\u00fck\u00fcn\u00fcz\u00fc azaltman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h2>\u0130leri D\u00fczey Optimizasyon ve G\u00fcvenlik \u0130pu\u00e7lar\u0131<\/h2>\n<p>KEDA HTTP Add-on'u temel d\u00fczeyde kurup \u00e7al\u0131\u015ft\u0131rd\u0131ktan sonra, daha iyi performans, daha fazla esneklik ve art\u0131r\u0131lm\u0131\u015f g\u00fcvenlik sa\u011flamak i\u00e7in baz\u0131 ileri d\u00fczey konulara odaklanabiliriz. Bu ipu\u00e7lar\u0131, KEDA da\u011f\u0131t\u0131m\u0131n\u0131zdan en iyi \u015fekilde yararlanman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h3>1. \u00d6l\u00e7eklenme Davran\u0131\u015f\u0131n\u0131 \u0130nce Ayarlamak: Cooldown ve Stabilization<\/h3>\n<p>Otomatik \u00f6l\u00e7eklendirmenin en \u00f6nemli y\u00f6nlerinden biri, gereksiz ve h\u0131zl\u0131 \u00f6l\u00e7eklenme (thrashing) veya tam tersi, \u00e7ok yava\u015f \u00f6l\u00e7eklenme davran\u0131\u015flar\u0131ndan ka\u00e7\u0131nmakt\u0131r. KEDA HTTP Add-on, bu davran\u0131\u015flar\u0131 HPA'n\u0131n (Horizontal Pod Autoscaler) sa\u011flad\u0131\u011f\u0131 yeteneklerle birle\u015ftirir.<\/p>\n<ul>\n<li><strong><code>cooldownPeriod<\/code>:<\/strong> <code>HTTPScaledObject<\/code> i\u00e7inde tan\u0131mlanan bu parametre, son istek i\u015flendikten veya metrikler d\u00fc\u015ft\u00fckten sonra pod say\u0131s\u0131n\u0131n minimuma d\u00fc\u015fmeden \u00f6nce beklenecek s\u00fcreyi (saniye cinsinden) belirler. K\u0131sa bir <code>cooldownPeriod<\/code>, h\u0131zl\u0131 \u00f6l\u00e7eklenmeyi sa\u011flar ancak h\u0131zl\u0131 d\u00fc\u015f\u00fc\u015fler nedeniyle gereksiz kaynak tahsisi ve b\u0131rakma d\u00f6ng\u00fclerine yol a\u00e7abilir. Genellikle 30-300 saniye aras\u0131nda bir de\u011fer kullan\u0131lmas\u0131 tavsiye edilir.<\/li>\n<li><strong><code>stabilizationWindowSeconds<\/code>:<\/strong> Bu, HPA'n\u0131n \u00f6l\u00e7eklenme karar\u0131 verirken ge\u00e7mi\u015f metrik verilerini ne kadar s\u00fcreyle g\u00f6z \u00f6n\u00fcnde bulunduraca\u011f\u0131n\u0131 belirleyen bir parametredir. \u00d6l\u00e7eklenmenin ani metrik dalgalanmalar\u0131 nedeniyle s\u00fcrekli art\u0131p azalmas\u0131n\u0131 (flapping) \u00f6nler. Daha y\u00fcksek bir de\u011fer, \u00f6l\u00e7eklenme kararlar\u0131n\u0131n daha yava\u015f ancak daha kararl\u0131 olmas\u0131n\u0131 sa\u011flar. \u00d6l\u00e7eklenmenin h\u0131zl\u0131 olmas\u0131n\u0131 istedi\u011fimizde, \u00f6zellikle <code>scaleUp<\/code> i\u00e7in bu de\u011feri d\u00fc\u015f\u00fcrebiliriz.<\/li>\n<li><strong>\u00d6l\u00e7eklenme Politikalar\u0131 (<code>policies<\/code>):<\/strong> <code>HTTPScaledObject<\/code> i\u00e7indeki <code>behavior<\/code> alan\u0131nda <code>scaleUp<\/code> ve <code>scaleDown<\/code> i\u00e7in y\u00fczdelik veya mutlak say\u0131 politikalar\u0131 tan\u0131mlayabilirsiniz. \u00d6rne\u011fin, her seferinde pod say\u0131s\u0131n\u0131 %100 oran\u0131nda art\u0131rmak veya 2 pod birden eklemek gibi. Bu, uygulamalar\u0131n\u0131z\u0131n y\u00fck art\u0131\u015flar\u0131na veya azal\u0131\u015flar\u0131na ne kadar agresif tepki verece\u011fini kontrol etmenizi sa\u011flar.<\/li>\n<\/ul>\n<div class=\"expert-tip\">\n <strong>Uzman \u0130pucu:<\/strong> Cooldown ve stabilization ayarlar\u0131n\u0131, uygulaman\u0131z\u0131n tipik trafik paternlerini ve ba\u015flang\u0131\u00e7 s\u00fcrelerini g\u00f6z \u00f6n\u00fcnde bulundurarak test edin ve optimize edin. H\u0131zl\u0131 ba\u015flayan (cold start) uygulamalar i\u00e7in daha agresif \u00f6l\u00e7eklenme politikalar\u0131 tercih edilebilirken, yava\u015f ba\u015flayan uygulamalar i\u00e7in daha uzun stabilization s\u00fcreleri faydal\u0131 olabilir.\n <\/div>\n<h3>2. G\u00fcvenlik Entegrasyonlar\u0131: TLS ve Yetkilendirme<\/h3>\n<p>KEDA HTTP Add-on, uygulaman\u0131z\u0131n \u00f6n\u00fcnde bir proxy g\u00f6revi g\u00f6rd\u00fc\u011f\u00fc i\u00e7in, bu bile\u015fenin g\u00fcvenli\u011fi kritik \u00f6neme sahiptir. \u00d6zellikle d\u0131\u015far\u0131dan eri\u015filebilir bir senaryoda TLS (Transport Layer Security) kullan\u0131m\u0131 \u015fartt\u0131r.<\/p>\n<ul>\n<li><strong>TLS Sonland\u0131rma:<\/strong> KEDA HTTP Add-on'un \u00f6n\u00fcne bir Ingress Controller (Nginx Ingress, Traefik, Istio Gateway vb.) yerle\u015ftirerek TLS sonland\u0131rmay\u0131 bu bile\u015fende yapabilirsiniz. Ingress Controller, d\u0131\u015far\u0131dan gelen \u015fifreli trafi\u011fi \u00e7\u00f6zer ve Add-on'a \u015fifresiz (veya i\u00e7 TLS ile tekrar \u015fifrelenmi\u015f) olarak iletir. Bu, yayg\u0131n ve g\u00fcvenli bir yakla\u015f\u0131md\u0131r.<\/li>\n<li><strong>\u0130\u00e7 \u0130leti\u015fim G\u00fcvenli\u011fi:<\/strong> E\u011fer KEDA HTTP Add-on ile uygulaman\u0131z aras\u0131ndaki ileti\u015fimde de \u015fifreleme istiyorsan\u0131z, uygulaman\u0131z\u0131n ve Add-on'un mTLS (mutual TLS) kullanmas\u0131n\u0131 yap\u0131land\u0131rman\u0131z gerekebilir. Bu, her iki taraf\u0131n da birbirinin kimli\u011fini do\u011frulamas\u0131na olanak tan\u0131r ve i\u00e7 a\u011fdaki yetkisiz eri\u015fimi engeller.<\/li>\n<li><strong>Yetkilendirme (Authorization):<\/strong> KEDA HTTP Add-on kendisi bir yetkilendirme katman\u0131 sunmasa da, \u00f6n\u00fcndeki bir API A\u011f Ge\u00e7idi veya Ingress Controller arac\u0131l\u0131\u011f\u0131yla OAuth2, JWT do\u011frulama gibi mekanizmalar\u0131 uygulayabilirsiniz. Bu, sadece yetkili kullan\u0131c\u0131lar\u0131n veya servislerin uygulaman\u0131za eri\u015febilmesini sa\u011flar.<\/li>\n<\/ul>\n<h3>3. \u00d6zel Metrikler ve Geli\u015fmi\u015f Entegrasyonlar<\/h3>\n<p>KEDA HTTP Add-on, ana i\u015flevini HTTP istek hacmine g\u00f6re \u00f6l\u00e7eklendirme olarak yerine getirirken, Prometheus gibi metrik sistemleriyle entegre olarak daha geli\u015fmi\u015f senaryolar\u0131 da destekler. KEDA'n\u0131n genel yetene\u011fi olan Custom Metrics Scaller'lar\u0131 kullanarak, HTTP Add-on'dan al\u0131nan metrikleri di\u011fer \u00f6zel metriklerle birle\u015ftirebilirsiniz.<\/p>\n<ul>\n<li><strong>Prometheus Entegrasyonu:<\/strong> KEDA HTTP Add-on, kendi metriklerini Prometheus format\u0131nda yay\u0131nlar. Bu metrikleri Prometheus ile toplayarak Grafana gibi ara\u00e7larla izleyebilir ve derinlemesine analiz yapabilirsiniz. Bu sayede, uygulaman\u0131z\u0131n \u00f6l\u00e7eklenme davran\u0131\u015f\u0131n\u0131 g\u00f6rselle\u015ftirebilir ve performans sorunlar\u0131n\u0131 daha kolay tespit edebilirsiniz.<\/li>\n<li><strong>Rate Limiting (Oran S\u0131n\u0131rlama):<\/strong> Baz\u0131 durumlarda, a\u015f\u0131r\u0131 istek y\u00fck\u00fcn\u00fcn sadece \u00f6l\u00e7eklendirme ile de\u011fil, ayn\u0131 zamanda oran s\u0131n\u0131rlama (rate limiting) ile de y\u00f6netilmesi gerekebilir. KEDA HTTP Add-on'un bir par\u00e7as\u0131 olmasa da, bir Ingress Controller (Nginx, Traefik) veya bir servis a\u011f\u0131 (Istio, Linkerd) \u00e7\u00f6z\u00fcm\u00fc ile birlikte kullanarak gelen istekleri belirli bir oranda s\u0131n\u0131rlayabilir ve uygulaman\u0131z\u0131 potansiyel k\u00f6t\u00fc niyetli sald\u0131r\u0131lardan veya a\u015f\u0131r\u0131 y\u00fcklenmeden koruyabilirsiniz. Bu, \u00f6l\u00e7eklenmeye ek bir koruma katman\u0131 sa\u011flar.<\/li>\n<\/ul>\n<p>Bu ileri d\u00fczey optimizasyon ve g\u00fcvenlik ipu\u00e7lar\u0131, KEDA HTTP Add-on da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n daha diren\u00e7li, g\u00fcvenli ve verimli olmas\u0131n\u0131 sa\u011flayacakt\u0131r. Her zaman oldu\u011fu gibi, de\u011fi\u015fiklikleri \u00fcretim ortam\u0131na uygulamadan \u00f6nce bir test ortam\u0131nda dikkatlice do\u011frulaman\u0131z \u00f6nemlidir.<\/p>\n<h2>Sonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<p>Bulut yerel mimarilerin h\u0131zla yayg\u0131nla\u015fmas\u0131yla birlikte, uygulamalar\u0131n dinamik ve verimli bir \u015fekilde \u00f6l\u00e7eklenmesi, rekabet avantaj\u0131 sa\u011flaman\u0131n ve kullan\u0131c\u0131 memnuniyetini art\u0131rman\u0131n temel ta\u015f\u0131 haline gelmi\u015ftir. KEDA HTTP Add-on, Kubernetes ekosistemindeki bu ihtiyaca g\u00fc\u00e7l\u00fc ve esnek bir yan\u0131t sunarak, geli\u015ftiricilerin ve operasyon ekiplerinin i\u015fini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde kolayla\u015ft\u0131rm\u0131\u015ft\u0131r. Makalemiz boyunca, KEDA'n\u0131n olay tabanl\u0131 \u00f6l\u00e7eklendirme g\u00fcc\u00fcn\u00fc, HTTP Add-on'un bu yetene\u011fi nas\u0131l HTTP tabanl\u0131 uygulamalara ta\u015f\u0131d\u0131\u011f\u0131n\u0131, ad\u0131m ad\u0131m kurulum ve yap\u0131land\u0131rma s\u00fcre\u00e7lerini ve ger\u00e7ek d\u00fcnya senaryolar\u0131ndaki uygulama alanlar\u0131n\u0131 detayl\u0131ca inceledik. Ayr\u0131ca, performans ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan ileri d\u00fczey optimizasyon ipu\u00e7lar\u0131 sunduk.<\/p>\n<p>KEDA HTTP Add-on'un en b\u00fcy\u00fck avantaj\u0131, uygulamalar\u0131n\u0131z\u0131n gelen HTTP isteklerinin ger\u00e7ek hacmine g\u00f6re an\u0131nda ve otomatik olarak \u00f6l\u00e7eklenmesini sa\u011flamas\u0131d\u0131r. Bu, sadece yo\u011fun trafik anlar\u0131nda bile kesintisiz bir kullan\u0131c\u0131 deneyimi sunmakla kalmaz, ayn\u0131 zamanda d\u00fc\u015f\u00fck trafik d\u00f6nemlerinde gereksiz kaynaklar\u0131n bo\u015fta kalmas\u0131n\u0131 engelleyerek bulut maliyetlerinde \u00f6nemli tasarruflar sa\u011flar. Mikroservisler, API a\u011f ge\u00e7itleri, e-ticaret siteleri ve medya portallar\u0131 gibi de\u011fi\u015fken i\u015f y\u00fcklerine sahip her t\u00fcrl\u00fc HTTP tabanl\u0131 uygulama i\u00e7in KEDA HTTP Add-on, modern ve verimli bir \u00f6l\u00e7eklendirme stratejisinin vazge\u00e7ilmez bir par\u00e7as\u0131d\u0131r. Otomasyon, verimlilik ve maliyet optimizasyonu hedeflendi\u011finde, KEDA HTTP Add-on, Kubernetes \u00fczerinde \u00e7al\u0131\u015fan uygulamalar i\u00e7in kesinlikle g\u00f6z \u00f6n\u00fcnde bulundurulmas\u0131 gereken bir \u00e7\u00f6z\u00fcmd\u00fcr.<\/p>\n<h3>S\u0131k\u00e7a Sorulan Sorular<\/h3>\n<dl>\n<dt><strong>1. KEDA HTTP Add-on sadece HTTP isteklerine mi duyarl\u0131d\u0131r? Ba\u015fka bir protokol\u00fc \u00f6l\u00e7eklendirebilir mi?<\/strong><\/dt>\n<dd>Evet, KEDA HTTP Add-on \u00f6zellikle HTTP\/HTTPS istek hacmini ve gecikme s\u00fcresini temel alarak \u00f6l\u00e7eklendirme yapar. KEDA'n\u0131n kendisi \u00e7e\u015fitli di\u011fer olay kaynaklar\u0131na (Kafka, RabbitMQ, SQS, Azure Service Bus vb.) duyarl\u0131 bir\u00e7ok farkl\u0131 scaler sunar. Ancak HTTP Add-on, yaln\u0131zca HTTP protokol\u00fc \u00fczerinden gelen talepleri izler ve \u00f6l\u00e7eklendirme i\u00e7in kullan\u0131r.<\/dd>\n<dt><strong>2. KEDA HTTP Add-on kullanmak Ingress Controller yerine mi ge\u00e7er?<\/strong><\/dt>\n<dd>Hay\u0131r, KEDA HTTP Add-on bir Ingress Controller'\u0131n yerine ge\u00e7mez, aksine onu tamamlar. Ingress Controller d\u0131\u015far\u0131dan gelen trafi\u011fi k\u00fcmenizdeki servislere y\u00f6nlendirme ve bazen TLS sonland\u0131rma gibi g\u00f6revleri \u00fcstlenirken, KEDA HTTP Add-on bu trafi\u011fin hacmine g\u00f6re uygulaman\u0131z\u0131n pod say\u0131s\u0131n\u0131 y\u00f6netir. Genellikle Ingress Controller'dan gelen trafik KEDA HTTP Add-on proxy'sine y\u00f6nlendirilir ve buradan uygulaman\u0131za ula\u015f\u0131r.<\/dd>\n<dt><strong>3. KEDA HTTP Add-on'un kurulumu karma\u015f\u0131k m\u0131d\u0131r ve ne kadar kaynak t\u00fcketir?<\/strong><\/dt>\n<dd>KEDA HTTP Add-on'un kurulumu Helm paket y\u00f6neticisi sayesinde olduk\u00e7a basittir ve genellikle birka\u00e7 komutla tamamlan\u0131r. Kendi ba\u015f\u0131na olduk\u00e7a hafif bir bile\u015fendir ve minimal kaynak t\u00fcketir. Bir kontrol\u00f6r (controller) pod'u ve bir veya daha fazla proxy (interceptor) pod'u \u00e7al\u0131\u015ft\u0131r\u0131r. Kaynak t\u00fcketimi, izledi\u011fi ana bilgisayar say\u0131s\u0131na ve trafik hacmine ba\u011fl\u0131 olarak de\u011fi\u015fmekle birlikte, genellikle k\u00fcmenizde ek bir y\u00fck olu\u015fturmaz.<\/dd>\n<dt><strong>4. Uygulamam\u0131n s\u0131f\u0131ra kadar \u00f6l\u00e7eklenmesi (scale-to-zero) m\u00fcmk\u00fcn m\u00fcd\u00fcr?<\/strong><\/dt>\n<dd>Evet, KEDA'n\u0131n temel \u00f6zelliklerinden biri scale-to-zero deste\u011fidir ve KEDA HTTP Add-on da bu \u00f6zelli\u011fi destekler. E\u011fer bir <code>HTTPScaledObject<\/code> tan\u0131mlam\u0131\u015f ve <code>minReplicas<\/code> de\u011ferini belirtmediyseniz veya 0 olarak ayarlad\u0131ysan\u0131z, belirli bir s\u00fcre boyunca hi\u00e7bir HTTP iste\u011fi al\u0131nmad\u0131\u011f\u0131nda uygulaman\u0131z\u0131n pod say\u0131s\u0131 s\u0131f\u0131ra d\u00fc\u015fecektir. \u0130lk istek geldi\u011finde ise KEDA podlar\u0131 tekrar aya\u011fa kald\u0131racakt\u0131r (cold start).<\/dd>\n<dt><strong>5. KEDA HTTP Add-on ile gecikme s\u00fcresine g\u00f6re \u00f6l\u00e7eklendirme yapabilir miyim?<\/strong><\/dt>\n<dd>Evet, KEDA HTTP Add-on, sadece istek say\u0131s\u0131na (requests per second) g\u00f6re de\u011fil, ayn\u0131 zamanda HTTP isteklerinin ortalama gecikme s\u00fcresine (latency) g\u00f6re de \u00f6l\u00e7eklendirme yapabilme yetene\u011fine sahiptir. <code>HTTPScaledObject<\/code> tan\u0131m\u0131n\u0131zda <code>type: latency<\/code> ve uygun metrik ayarlar\u0131n\u0131 kullanarak bu \u00f6zelli\u011fi yap\u0131land\u0131rabilirsiniz. Bu, \u00f6zellikle hassas yan\u0131t s\u00fcreleri gerektiren uygulamalar i\u00e7in \u00e7ok faydal\u0131d\u0131r.<\/dd>\n<\/dl>\n<p><\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya…","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":[1],"tags":[],"class_list":{"0":"post-35352","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","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>KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme<\/title>\n<meta name=\"description\" content=\"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.\" \/>\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\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme\" \/>\n<meta property=\"og:description\" content=\"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-28T15:01:46+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=\"26 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme\",\"datePublished\":\"2025-11-28T15:01:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\"},\"wordCount\":4883,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\",\"name\":\"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-28T15:01:46+00:00\",\"description\":\"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme\"}]},{\"@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":"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme","description":"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.","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\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/","og_locale":"tr_TR","og_type":"article","og_title":"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme","og_description":"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.","og_url":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-28T15:01:46+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"26 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme","datePublished":"2025-11-28T15:01:46+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/"},"wordCount":4883,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/","url":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/","name":"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-28T15:01:46+00:00","description":"Modern bulut yerel uygulamalar\u0131 geli\u015ftirirken, talep dalgalanmalar\u0131yla ba\u015fa \u00e7\u0131kmak ve kaynaklar\u0131 verimli kullanmak kritik \u00f6neme sahiptir. Peki ya uygulamalar\u0131n\u0131z yo\u011fun istekler alt\u0131nda yava\u015fl\u0131yor ve maliyetleriniz kontrol\u00fcn\u00fczden \u00e7\u0131k\u0131yorsa ne yapmal\u0131s\u0131n\u0131z? KEDA HTTP Add-on, bu zorluklar\u0131 a\u015farak uygulamalar\u0131n\u0131z\u0131n gelen HTTP istek hacmine g\u00f6re dinamik olarak \u00f6l\u00e7eklenmesini sa\u011flar, b\u00f6ylece hem performans\u0131 art\u0131r\u0131r hem de bulut maliyetlerini optimize eder.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/keda-http-add-on-ile-istek-temelli-dinamik-olceklendirme\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"KEDA HTTP Add-on ile \u0130stek Temelli Dinamik \u00d6l\u00e7eklendirme"}]},{"@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\/35352","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=35352"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/35352\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=35352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=35352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=35352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}