{"id":249,"date":"2026-11-18T15:34:00","date_gmt":"2026-11-18T15:34:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/?p=249"},"modified":"2026-11-18T15:34:00","modified_gmt":"2026-11-18T15:34:00","slug":"spring-boot-production-checklist","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/18\/spring-boot-production-checklist\/","title":{"rendered":"Spring Boot Uygulamas\u0131n\u0131 Production&#8217;a Haz\u0131rlamak: Kontrol Listesi"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Spring Boot production<\/strong> haz\u0131rl\u0131\u011f\u0131, lokalde sorunsuz \u00e7al\u0131\u015fan bir uygulaman\u0131n ger\u00e7ek trafik, deploy&#8217;lar, ar\u0131zalar ve g\u00fcvenlik tehditleri alt\u0131nda da \u00f6ng\u00f6r\u00fclebilir davranmas\u0131n\u0131 sa\u011flamak i\u00e7in yap\u0131lan ayarlar\u0131n b\u00fct\u00fcn\u00fcd\u00fcr. Spring Boot bir\u00e7ok \u015feyi varsay\u0131lan olarak do\u011fru yapar. Ama baz\u0131 kritik ayarlar bilin\u00e7li olarak a\u00e7\u0131lmad\u0131k\u00e7a kapal\u0131 kal\u0131r ve eksiklikleri genellikle ilk ciddi olayda fark edilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yaz\u0131da yeni bir servisi production&#8217;a \u00e7\u0131karmadan \u00f6nce kendi kulland\u0131\u011f\u0131m kontrol listesini payla\u015f\u0131yorum. Her maddenin arkas\u0131ndaki gerek\u00e7eyi de k\u0131saca anlatt\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Health check&#8217;ler do\u011fru ayr\u0131lm\u0131\u015f m\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot Actuator, Kubernetes i\u00e7in ayr\u0131 readiness ve liveness endpoint&#8217;leri sunar:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>management.endpoint.health.probes.enabled=true<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>\/actuator\/health\/liveness\n\/actuator\/health\/readiness<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ikisinin farkl\u0131 sorular sordu\u011funu bilmek \u00f6nemli. Readiness, &#8220;bu pod \u015fu anda trafik almaya haz\u0131r m\u0131?&#8221; sorusunu cevaplar. Liveness ise &#8220;bu pod kurtar\u0131lamaz bir durumda m\u0131, yeniden ba\u015flat\u0131lmal\u0131 m\u0131?&#8221; sorusunu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">En s\u0131k yap\u0131lan hata, veritaban\u0131 kontrol\u00fcn\u00fc liveness&#8217;a eklemektir. Veritaban\u0131 k\u0131sa s\u00fcreli\u011fine eri\u015filemez oldu\u011funda b\u00fct\u00fcn pod&#8217;lar ayn\u0131 anda yeniden ba\u015flat\u0131l\u0131r. Veritaban\u0131 geri geldi\u011finde ise so\u011fuk ba\u015flayan onlarca pod ile kar\u015f\u0131la\u015f\u0131r. D\u0131\u015f ba\u011f\u0131ml\u0131l\u0131klar liveness&#8217;ta de\u011fil, gerekiyorsa readiness&#8217;ta kontrol edilmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">JVM uygulamalar\u0131n\u0131n a\u00e7\u0131l\u0131\u015f s\u00fcresi de hesaba kat\u0131lmal\u0131. Uzun a\u00e7\u0131lan bir uygulamada liveness probe&#8217;un erken ba\u015far\u0131s\u0131z olmas\u0131n\u0131 engellemek i\u00e7in <code>startupProbe<\/code> tan\u0131mlamak gerekir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Graceful shutdown a\u00e7\u0131k m\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deploy s\u0131ras\u0131nda yar\u0131da kesilen istekler, bir\u00e7ok ekibin &#8220;kabul edilebilir&#8221; sayd\u0131\u011f\u0131 ama asl\u0131nda \u00f6nlenebilir bir problem.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>server.shutdown=graceful\nspring.lifecycle.timeout-per-shutdown-phase=20s<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ayar a\u00e7\u0131k oldu\u011funda uygulama, kapanma sinyali geldi\u011finde yeni istek kabul etmeyi b\u0131rak\u0131r ve devam eden isteklerin bitmesini bekler. Kubernetes taraf\u0131nda preStop beklemesi ve <code>terminationGracePeriodSeconds<\/code> ile birlikte d\u00fc\u015f\u00fcn\u00fclmesi gerekir. Bu s\u00fcrelerin nas\u0131l uyumlu hale getirilece\u011fini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/24\/kubernetes-graceful-shutdown-readiness\/\">Kubernetes&#8217;te graceful shutdown<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 anlatt\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Konfig\u00fcrasyon ba\u015flang\u0131\u00e7ta do\u011frulan\u0131yor mu?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eksik veya hatal\u0131 bir konfig\u00fcrasyon de\u011feri, uygulaman\u0131n a\u00e7\u0131l\u0131\u015fta de\u011fil ilk kullan\u0131mda hata vermesine neden olursa, deploy ba\u015far\u0131l\u0131 g\u00f6r\u00fcn\u00fcr ama sistem bozuktur.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@ConfigurationProperties(prefix = \"payment\")\n@Validated\npublic record PaymentProperties(\n    @NotNull URI baseUrl,\n    @NotNull Duration timeout\n) {}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>@Validated<\/code> ile zorunlu de\u011ferler ba\u015flang\u0131\u00e7ta kontrol edilir. Eksik bir de\u011fer, uygulaman\u0131n hi\u00e7 a\u00e7\u0131lmamas\u0131na ve rolling deploy&#8217;un eski versiyonda kalmas\u0131na yol a\u00e7ar. Hatan\u0131n kullan\u0131c\u0131ya ula\u015fmadan yakalanmas\u0131 tam olarak istenen \u015fey. Konfig\u00fcrasyonun ortamlara g\u00f6re ayr\u0131lmas\u0131 konusunu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/01\/application-configuration-environments\/\">konfig\u00fcrasyon ve ortam de\u011fi\u015fkenleri<\/a> yaz\u0131s\u0131nda ele alm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Secret&#8217;lar\u0131n properties dosyalar\u0131nda de\u011fil, ortam de\u011fi\u015fkenleri veya bir secret y\u00f6neticisi \u00fczerinden gelmesi de bu maddenin par\u00e7as\u0131. Neden \u00f6nemli oldu\u011funu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/09\/secret-management-api-keys-git\/\">secret y\u00f6netimi<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Timeout&#8217;lar tan\u0131ml\u0131 m\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot&#8217;un ve kulland\u0131\u011f\u0131 HTTP client&#8217;lar\u0131n baz\u0131 varsay\u0131lan timeout de\u011ferleri \u00e7ok uzun veya sonsuzdur. D\u0131\u015f bir servisin yava\u015flamas\u0131, timeout tan\u0131mlanmam\u0131\u015f bir client y\u00fcz\u00fcnden b\u00fct\u00fcn uygulamay\u0131 kilitleyebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kontrol edilmesi gereken yerler:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>HTTP client&#8217;lar i\u00e7in connect ve read timeout.<\/li>\n\n\n<li>Veritaban\u0131 connection pool&#8217;u i\u00e7in <code>connection-timeout<\/code>.<\/li>\n\n\n<li>Sorgular i\u00e7in transaction veya statement timeout.<\/li>\n\n\n<li>Mesaj consumer&#8217;lar\u0131 i\u00e7in i\u015fleme s\u00fcresi limitleri.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Hi\u00e7bir d\u0131\u015f \u00e7a\u011fr\u0131 s\u0131n\u0131rs\u0131z beklememeli. Timeout&#8217;un neden bir hata de\u011fil, belirsizlik oldu\u011funu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/28\/timeout-unknown-outcome\/\">timeout ve belirsiz sonu\u00e7<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Connection pool boyutu bilin\u00e7li se\u00e7ilmi\u015f mi?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">HikariCP&#8217;nin varsay\u0131lan havuz boyutu 10&#8217;dur. Bu de\u011fer bir\u00e7ok uygulama i\u00e7in makul bir ba\u015flang\u0131\u00e7, ama instance say\u0131s\u0131 ile birlikte d\u00fc\u015f\u00fcn\u00fclmeli. 20 instance ve her birinde 30 connection, veritaban\u0131n\u0131n kald\u0131rabilece\u011finden fazla olabilir. <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/28\/database-connection-pool-sizing\/\">Connection pool boyutland\u0131rma<\/a> yaz\u0131s\u0131nda bu hesab\u0131n nas\u0131l yap\u0131laca\u011f\u0131n\u0131 anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Loglar production i\u00e7in uygun mu?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Lokalde okunabilir d\u00fcz metin loglar faydal\u0131d\u0131r. Production&#8217;da ise loglar bir log sistemine g\u00f6nderilir ve orada aran\u0131r, filtrelenir. Structured logging bu y\u00fczden \u00f6nemli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring Boot 3.4 ile structured logging yerle\u015fik olarak geldi:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>logging.structured.format.console=ecs<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Kontrol edilmesi gereken di\u011fer konular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log seviyesi production&#8217;da <code>INFO<\/code> mu? <code>DEBUG<\/code> a\u00e7\u0131k kalm\u0131\u015f m\u0131?<\/li>\n\n\n<li>Her log sat\u0131r\u0131nda trace ID var m\u0131?<\/li>\n\n\n<li>Ki\u015fisel veri, token veya parola loglan\u0131yor mu?<\/li>\n\n\n<li>Request ve response g\u00f6vdesini loglayan bir filtre a\u00e7\u0131k kalm\u0131\u015f m\u0131?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ki\u015fisel verilerin loglara nas\u0131l s\u0131zd\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/03\/logging-personal-data-kvkk\/\">KVKK a\u00e7\u0131s\u0131ndan loglama<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 ele ald\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Metrik ve trace&#8217;ler toplan\u0131yor mu?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Actuator ve Micrometer, HTTP istekleri, JVM, connection pool ve cache i\u00e7in haz\u0131r metrikler sunar. Bunlar\u0131 Prometheus format\u0131nda d\u0131\u015far\u0131 a\u00e7mak tek bir ba\u011f\u0131ml\u0131l\u0131k ve bir ayar:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>management.endpoints.web.exposure.include=health,info,prometheus\nmanagement.metrics.distribution.percentiles-histogram.http.server.requests=true<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130kinci sat\u0131r \u00f6nemli. Histogram olmadan y\u00fczdelik de\u011ferler instance&#8217;lar aras\u0131nda do\u011fru \u015fekilde birle\u015ftirilemez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Trace&#8217;ler i\u00e7in Micrometer Tracing ve OpenTelemetry exporter&#8217;\u0131, servisler aras\u0131 \u00e7a\u011fr\u0131lar\u0131n ayn\u0131 trace alt\u0131nda g\u00f6r\u00fcnmesini sa\u011flar. Bu \u00fc\u00e7 sinyalin birlikte nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/04\/observability-logs-metrics-traces\/\">log, metric ve trace<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Actuator endpoint&#8217;leri g\u00fcvende mi?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu madde g\u00fcvenlik a\u00e7\u0131s\u0131ndan listedeki en kritik madde olabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>\/actuator\/env<\/code> ortam de\u011fi\u015fkenlerini, <code>\/actuator\/heapdump<\/code> bellekteki her \u015feyi, parolalar ve token&#8217;lar dahil, d\u0131\u015far\u0131 verebilir. <code>\/actuator\/loggers<\/code> log seviyesini de\u011fi\u015ftirmeye izin verir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Benim tercih etti\u011fim yap\u0131 \u015fu:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>D\u0131\u015far\u0131ya sadece <code>health<\/code> ve gerekirse <code>info<\/code> a\u00e7\u0131k.<\/li>\n\n\n<li>Di\u011fer actuator endpoint&#8217;leri ayr\u0131 bir management portunda ve sadece i\u00e7 a\u011fdan eri\u015filebilir.<\/li>\n\n\n<li><code>management.server.port<\/code> ile uygulama portundan ayr\u0131lm\u0131\u015f.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>management.server.port=8081\nmanagement.endpoints.web.exposure.include=health,info,prometheus<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ingress veya load balancer yaln\u0131zca uygulama portunu d\u0131\u015far\u0131ya a\u00e7ar. Prometheus ise i\u00e7 a\u011fdan management portuna eri\u015fir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bellek ayarlar\u0131 container&#8217;a uygun mu?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Container&#8217;da \u00e7al\u0131\u015fan Java uygulamalar\u0131nda en s\u0131k g\u00f6r\u00fclen problemlerden biri, heap&#8217;in container limitine e\u015fit ayarlanmas\u0131 ve pod&#8217;un OOMKilled olmas\u0131d\u0131r. JVM heap d\u0131\u015f\u0131nda da bellek kullan\u0131r.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=70<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do\u011fru oran\u0131n nas\u0131l bulunaca\u011f\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/05\/jvm-memory-container-limits\/\">container&#8217;da Java bellek ayarlar\u0131<\/a> yaz\u0131s\u0131nda anlatt\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Veritaban\u0131 migration&#8217;lar\u0131 g\u00fcvenli mi?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rolling deploy s\u0131ras\u0131nda eski ve yeni versiyon bir s\u00fcre ayn\u0131 \u015femay\u0131 kullan\u0131r. Bir kolonu silen veya yeniden adland\u0131ran migration, eski versiyonun hata vermesine neden olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Flyway veya Liquibase migration&#8217;lar\u0131n\u0131n her birinin bir \u00f6nceki uygulama versiyonuyla uyumlu olmas\u0131 gerekir. Bu konunun ayr\u0131nt\u0131lar\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/30\/zero-downtime-database-migration-expand-contract\/\">kesintisiz veritaban\u0131 migration&#8217;\u0131<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ba\u011f\u0131ml\u0131l\u0131klar ve g\u00fcvenlik g\u00fcncellemeleri takip ediliyor mu?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir Spring Boot uygulamas\u0131, do\u011frudan eklenen birka\u00e7 ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n arkas\u0131nda y\u00fczlerce dolayl\u0131 k\u00fct\u00fcphane ta\u015f\u0131r. Bunlardan birinde \u00e7\u0131kan bir g\u00fcvenlik a\u00e7\u0131\u011f\u0131, uygulaman\u0131n kendi kodunda hi\u00e7bir hata olmasa bile onu savunmas\u0131z b\u0131rak\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Production&#8217;a \u00e7\u0131kmadan \u00f6nce iki \u015feyin haz\u0131r olmas\u0131n\u0131 istiyorum. Birincisi, ba\u011f\u0131ml\u0131l\u0131klar\u0131 d\u00fczenli olarak tarayan bir ara\u00e7. OWASP Dependency-Check, GitHub&#8217;\u0131n Dependabot&#8217;u veya Renovate bu i\u015f i\u00e7in yayg\u0131n se\u00e7enekler. \u0130kincisi, Spring Boot&#8217;un desteklenen bir s\u00fcr\u00fcm\u00fcnde olmak. Deste\u011fi biten s\u00fcr\u00fcmler g\u00fcvenlik yamalar\u0131n\u0131 almaz ve b\u00fcy\u00fck versiyon atlamalar\u0131 zamanla zorla\u015f\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">K\u00fc\u00e7\u00fck ve s\u0131k g\u00fcncellemeler, y\u0131lda bir yap\u0131lan b\u00fcy\u00fck ve riskli g\u00fcncellemelerden \u00e7ok daha az ac\u0131 verir. Testlerin bu g\u00fcncellemeleri g\u00fcvenle yapacak kadar kapsaml\u0131 olmas\u0131 da i\u015fin par\u00e7as\u0131. Veritaban\u0131 i\u00e7eren testlerin neden ger\u00e7ek veritaban\u0131yla \u00e7al\u0131\u015fmas\u0131 gerekti\u011fini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/27\/testcontainers-instead-of-h2\/\">Testcontainers<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hata cevaplar\u0131 tutarl\u0131 m\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Production&#8217;da bir exception&#8217;\u0131n stack trace&#8217;iyle birlikte client&#8217;a d\u00f6nmesi hem g\u00fcvenlik hem kullan\u0131c\u0131 deneyimi problemi. Spring Boot&#8217;un varsay\u0131lan hata sayfas\u0131 baz\u0131 ayarlarda i\u00e7 detaylar\u0131 g\u00f6sterebilir.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>server.error.include-stacktrace=never\nserver.error.include-message=never\nspring.mvc.problemdetails.enabled=true<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Son ayar, Spring&#8217;in kendi \u00fcretti\u011fi hatalar\u0131 da standart Problem Details format\u0131nda d\u00f6nd\u00fcr\u00fcr. Uygulaman\u0131n tamam\u0131nda tek bir hata format\u0131 kullanmak, client&#8217;lar\u0131n i\u015fini kolayla\u015ft\u0131r\u0131r ve beklenmedik bilgi s\u0131z\u0131nt\u0131s\u0131n\u0131 \u00f6nler.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kontrol listesi \u00f6zeti<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Alan<\/th><th>Kontrol<\/th><\/tr><\/thead><tbody><tr><td>Health<\/td><td>Readiness ve liveness ayr\u0131, liveness d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131k i\u00e7ermiyor<\/td><\/tr><tr><td>Shutdown<\/td><td><code>server.shutdown=graceful<\/code>, preStop ve grace period uyumlu<\/td><\/tr><tr><td>Konfig\u00fcrasyon<\/td><td><code>@Validated<\/code>, zorunlu de\u011ferler, secret&#8217;lar d\u0131\u015far\u0131da<\/td><\/tr><tr><td>Timeout<\/td><td>B\u00fct\u00fcn d\u0131\u015f \u00e7a\u011fr\u0131larda tan\u0131ml\u0131<\/td><\/tr><tr><td>Connection pool<\/td><td>Instance say\u0131s\u0131yla birlikte hesaplanm\u0131\u015f<\/td><\/tr><tr><td>Loglama<\/td><td>Structured, trace ID&#8217;li, ki\u015fisel veri yok<\/td><\/tr><tr><td>Metrik<\/td><td>Prometheus, histogram a\u00e7\u0131k<\/td><\/tr><tr><td>Actuator<\/td><td>Ayr\u0131 port, d\u0131\u015far\u0131ya sadece health<\/td><\/tr><tr><td>Bellek<\/td><td><code>MaxRAMPercentage<\/code>, container limitine g\u00f6re<\/td><\/tr><tr><td>Migration<\/td><td>\u00d6nceki versiyonla uyumlu<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Actuator&#8217;un sundu\u011fu b\u00fct\u00fcn \u00f6zellikler ve ayarlar Spring Boot&#8217;un <a href=\"https:\/\/docs.spring.io\/spring-boot\/reference\/actuator\/index.html\" target=\"_blank\" rel=\"noopener\">resmi Actuator dok\u00fcmantasyonunda<\/a> yer al\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu listenin hi\u00e7bir maddesi tek ba\u015f\u0131na zor de\u011fil. Zor olan, bunlar\u0131 yeni bir servis a\u00e7\u0131ld\u0131\u011f\u0131nda her seferinde hat\u0131rlamak. Bu y\u00fczden ben bu ayarlar\u0131 bir proje \u015fablonuna veya ortak bir starter mod\u00fcl\u00fcne koymay\u0131 tercih ediyorum. B\u00f6ylece her yeni servis, production&#8217;a haz\u0131r varsay\u0131lanlarla ba\u015fl\u0131yor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Spring Boot production haz\u0131rl\u0131\u011f\u0131 i\u00e7in kontrol listesi: health check, graceful shutdown, konfig\u00fcrasyon, timeout, loglama, Actuator g\u00fcvenli\u011fi ve bellek.<\/p>\n","protected":false},"author":1,"featured_media":248,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-249","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mimari"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=249"}],"version-history":[{"count":1,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/249\/revisions"}],"predecessor-version":[{"id":284,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/249\/revisions\/284"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/248"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}