{"id":34912,"date":"2025-11-23T15:01:47","date_gmt":"2025-11-23T12:01:47","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/spring-bean-yasam-dongusu-adim-adim-rehber\/"},"modified":"2025-11-23T15:01:47","modified_gmt":"2025-11-23T12:01:47","slug":"spring-bean-yasam-dongusu-adim-adim-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/spring-bean-yasam-dongusu-adim-adim-rehber\/","title":{"rendered":"Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc: Ad\u0131m Ad\u0131m Rehber"},"content":{"rendered":"

Modern Java uygulamalar\u0131 geli\u015ftirirken, Spring Framework’\u00fcn kalbinde yer alan bean’lerin nas\u0131l y\u00f6netildi\u011fini anlamak, performans\u0131 optimize etmek ve kodunuzu daha s\u00fcrd\u00fcr\u00fclebilir hale getirmek i\u00e7in kritik bir \u00f6neme sahiptir. Peki, bu bean’ler Spring konteyneri taraf\u0131ndan tam olarak nas\u0131l olu\u015fturulur, yap\u0131land\u0131r\u0131l\u0131r, kullan\u0131l\u0131r ve sonunda nas\u0131l yok edilir? Bu s\u00fcre\u00e7, yani Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc<\/strong>, uygulama kaynaklar\u0131n\u0131n etkin y\u00f6netimi ve stabil \u00e7al\u0131\u015fmas\u0131 a\u00e7\u0131s\u0131ndan hayati bir rol oynar. Bu makalede, Spring bean ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn her ad\u0131m\u0131n\u0131 detayl\u0131 bir \u015fekilde inceleyecek, pratik \u00f6rneklerle peki\u015ftirecek ve bu s\u00fcrece tam olarak hakim olman\u0131z\u0131 sa\u011flayacak bilgiler sunaca\u011f\u0131z. B\u00f6ylece, uygulaman\u0131z\u0131n ba\u015flang\u0131c\u0131ndan sonuna kadar bean’lerinizin davran\u0131\u015flar\u0131n\u0131 \u00f6ng\u00f6rebilir ve kontrol edebilirsiniz.<\/p>\n

Bir Spring uygulamas\u0131nda, bean’ler i\u015f mant\u0131\u011f\u0131n\u0131z\u0131n temel yap\u0131 ta\u015flar\u0131d\u0131r. Veritaban\u0131 ba\u011flant\u0131lar\u0131ndan i\u015f servislerine, g\u00fcvenlik filtrelerinden kullan\u0131c\u0131 aray\u00fcz\u00fc bile\u015fenlerine kadar bir\u00e7ok farkl\u0131 g\u00f6revi \u00fcstlenebilirler. Bu bile\u015fenlerin do\u011fru zamanda ba\u015flat\u0131lmas\u0131, ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131n enjekte edilmesi ve sonunda sistemden d\u00fczg\u00fcn bir \u015fekilde \u00e7\u0131kar\u0131lmas\u0131 gerekmektedir. Aksi takdirde, kaynak s\u0131z\u0131nt\u0131lar\u0131, bellek ta\u015fmalar\u0131 veya beklenmedik uygulama hatalar\u0131 gibi ciddi sorunlarla kar\u015f\u0131la\u015fabilirsiniz. \u0130\u015fte bu noktada Spring’in sundu\u011fu ya\u015fam d\u00f6ng\u00fcs\u00fc mekanizmalar\u0131 devreye girer. Bu mekanizmalar sayesinde, bir bean’in \u00f6mr\u00fc boyunca belirli olaylara yan\u0131t verecek kodlar\u0131 tan\u0131mlayabilir, b\u00f6ylece uygulaman\u0131z\u0131n stabilitesini ve verimlili\u011fini art\u0131rabilirsiniz. Sonu\u00e7 olarak, Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc’n\u00fc anlamak, sadece iyi bir Spring geli\u015ftiricisi olman\u0131n de\u011fil, ayn\u0131 zamanda robust ve \u00f6l\u00e7eklenebilir uygulamalar in\u015fa etmenin de temelini olu\u015fturur.<\/p>\n

Bu ya\u015fam d\u00f6ng\u00fcs\u00fcne hakim olmak, \u00f6zellikle b\u00fcy\u00fck \u00f6l\u00e7ekli ve karma\u015f\u0131k projelerde ortaya \u00e7\u0131kan sorunlar\u0131 gidermede size \u00f6nemli avantajlar sa\u011flar. \u00d6rne\u011fin, bir bean’in ba\u015flat\u0131lmas\u0131 s\u0131ras\u0131nda harici bir hizmete ba\u011flanmas\u0131 gerekiyorsa, bu ba\u011flant\u0131n\u0131n ne zaman kuruldu\u011funu ve ba\u015far\u0131s\u0131z olursa nas\u0131l ele al\u0131naca\u011f\u0131n\u0131 tam olarak bilmeniz gerekir. Ayn\u0131 \u015fekilde, uygulama kapat\u0131l\u0131rken a\u00e7\u0131lan kaynaklar\u0131n (dosya tan\u0131t\u0131c\u0131lar\u0131, a\u011f ba\u011flant\u0131lar\u0131 gibi) d\u00fczg\u00fcn bir \u015fekilde kapat\u0131lmas\u0131, sistemin temiz bir \u015fekilde sonlanmas\u0131 i\u00e7in elzemdir. Spring’in sa\u011flad\u0131\u011f\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fc geri \u00e7a\u011f\u0131rma y\u00f6ntemleri, bu t\u00fcr i\u015flemleri otomatikle\u015ftirmek ve y\u00f6netmek i\u00e7in g\u00fc\u00e7l\u00fc bir \u00e7er\u00e7eve sunar. Dolay\u0131s\u0131yla, bu konuyu derinlemesine kavramak, sadece Spring uygulamalar\u0131n\u0131z\u0131 daha iyi anlaman\u0131za de\u011fil, ayn\u0131 zamanda daha g\u00fcvenilir ve bak\u0131m\u0131 kolay sistemler geli\u015ftirmenize de yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n

Spring IoC Konteyneri ve Bean’ler: Temel Kavramlara Derinlemesine Bir Bak\u0131\u015f<\/h2>\n

Spring Framework’\u00fcn merkezinde “Inversion of Control” (IoC) veya di\u011fer ad\u0131yla “Dependency Injection” (DI) prensibi yer al\u0131r. Geleneksel uygulama geli\u015ftirmede, bir nesne genellikle kendi ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 kendisi olu\u015fturur veya bulur. Ancak IoC prensibiyle bu durum tersine d\u00f6ner: nesneler kendi ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 y\u00f6netmez, bunun yerine ba\u011f\u0131ml\u0131l\u0131klar\u0131 d\u0131\u015far\u0131dan, yani bir IoC konteyneri taraf\u0131ndan sa\u011flan\u0131r. Spring konteyneri, uygulamam\u0131zdaki nesnelerin ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc y\u00f6neten g\u00fc\u00e7l\u00fc bir yap\u0131d\u0131r. Bu konteyner, nesneleri olu\u015fturmaktan, onlar\u0131n aras\u0131ndaki ba\u011f\u0131ml\u0131l\u0131klar\u0131 \u00e7\u00f6zmeye ve sonunda onlar\u0131 yok etmeye kadar t\u00fcm s\u00fcreci denetler. B\u00f6ylece geli\u015ftiriciler, ba\u011f\u0131ml\u0131l\u0131k y\u00f6netimi yerine i\u015f mant\u0131\u011f\u0131na odaklanabilirler.<\/p>\n

Peki, bu konteyner taraf\u0131ndan y\u00f6netilen nesnelere ne isim veriyoruz? Cevap: Bean<\/strong>. Spring kontekstinde bir “bean”, Spring IoC konteyneri taraf\u0131ndan ba\u015flat\u0131lan, birle\u015ftirilen ve y\u00f6netilen herhangi bir nesnedir. Bir bean temelde bir POJO (Plain Old Java Object) olup, Spring konfig\u00fcrasyonunuzda (XML, Java Config veya annotation tabanl\u0131) tan\u0131mlanm\u0131\u015f ve Spring’in \u00f6zel yetenekleriyle donat\u0131lm\u0131\u015ft\u0131r. Bu bean’ler, uygulama i\u00e7inde belirli g\u00f6revleri yerine getiren bile\u015fenleri temsil eder. \u00d6rne\u011fin, bir UserService<\/code> bean’i kullan\u0131c\u0131larla ilgili i\u015f mant\u0131\u011f\u0131n\u0131 y\u00f6netirken, bir UserRepository<\/code> bean’i veritaban\u0131 i\u015flemlerinden sorumlu olabilir. Spring konteyneri, bu bean’lerin tekil \u00f6rneklerini (singleton) olu\u015fturabilir, her istek i\u00e7in yeni bir \u00f6rnek (prototype) sa\u011flayabilir veya daha \u00f6zel kapsamlar (request, session gibi) tan\u0131mlayabilir.<\/p>\n

Spring konteyneri, uygulaman\u0131n ba\u015flat\u0131lmas\u0131yla birlikte bean tan\u0131mlar\u0131n\u0131 okur ve bu tan\u0131mlara g\u00f6re bean’leri olu\u015fturur. Bu i\u015flem s\u0131ras\u0131nda, bir bean’in ihtiya\u00e7 duydu\u011fu di\u011fer bean’ler (ba\u011f\u0131ml\u0131l\u0131klar\u0131) otomatik olarak enjekte edilir. Bu ba\u011f\u0131ml\u0131l\u0131k enjeksiyonu, kodunuzu daha mod\u00fcler, test edilebilir ve yeniden kullan\u0131labilir hale getirir. \u00d6rne\u011fin, UserService<\/code> bean’i bir UserRepository<\/code> bean’ine ihtiya\u00e7 duydu\u011funda, Spring konteyneri bu ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 sizin yerinize sa\u011flar. Bu sayede, UserService<\/code> s\u0131n\u0131f\u0131 UserRepository<\/code>‘nin nas\u0131l olu\u015fturuldu\u011fu veya y\u00f6netildi\u011fi hakk\u0131nda hi\u00e7bir bilgiye sahip olmak zorunda kalmaz. Bu ayr\u0131m, uygulaman\u0131n karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r ve de\u011fi\u015fikliklere kar\u015f\u0131 daha diren\u00e7li olmas\u0131n\u0131 sa\u011flar. IoC ve Bean kavramlar\u0131, Spring Framework’\u00fcn temel ta\u015flar\u0131d\u0131r ve bean ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc anlaman\u0131n ilk ad\u0131m\u0131d\u0131r. Ayr\u0131ca, Spring’in ApplicationContext<\/code> ve BeanFactory<\/code> gibi konteyner aray\u00fczleri, bean’lerin y\u00f6netilmesinde farkl\u0131 seviyelerde yetenekler sunar; ApplicationContext<\/code> daha zengin \u00f6zelliklere sahiptir ve modern Spring uygulamalar\u0131nda tercih edilen se\u00e7enektir.<\/p>\n

Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fcn\u00fcn Temel Ad\u0131mlar\u0131: Kapsaml\u0131 Bir Rehber<\/h2>\n

Spring bean ya\u015fam d\u00f6ng\u00fcs\u00fc, bir bean’in konteyner taraf\u0131ndan olu\u015fturulmas\u0131ndan yok edilmesine kadar ge\u00e7en s\u00fcreci ifade eder. Bu s\u00fcre\u00e7, uygulaman\u0131z\u0131n davran\u0131\u015f\u0131n\u0131 ve kaynak kullan\u0131m\u0131n\u0131 do\u011frudan etkiledi\u011fi i\u00e7in her ad\u0131m\u0131n\u0131 anlamak b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. \u0130\u015fte Spring bean ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn temel ad\u0131mlar\u0131:<\/p>\n

    \n
  1. \n

    Bean’in Yarat\u0131lmas\u0131 (Instantiation):<\/h3>\n

    Spring konteyneri, bir bean tan\u0131m\u0131n\u0131 (XML, Java Config veya annotation’lar arac\u0131l\u0131\u011f\u0131yla) okudu\u011funda, ilk olarak o bean s\u0131n\u0131f\u0131n\u0131n bir \u00f6rne\u011fini olu\u015fturur. Bu genellikle varsay\u0131lan bir kurucu metot (constructor) \u00e7a\u011fr\u0131larak yap\u0131l\u0131r. E\u011fer varsay\u0131lan bir kurucu metot yoksa veya belirli parametrelerle bir kurucu metot kullan\u0131lmas\u0131 gerekiyorsa, Spring bunu da y\u00f6netebilir.<\/p>\n

    \u00d6rne\u011fin, @Component<\/code> ile i\u015faretlenmi\u015f bir s\u0131n\u0131f\u0131n\u0131z varsa:<\/p>\n

    \npackage com.example.service;\n\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class MyService {\n    public MyService() {\n        System.out.println(\"1. MyService bean'i yarat\u0131ld\u0131 (constructor).\");\n    }\n    \/\/ ... di\u011fer metotlar\n}\n        <\/pre>\n
    <\/code><\/p>\n
    Bu a\u015famada bean sadece ham bir nesnedir, hen\u00fcz ba\u011f\u0131ml\u0131l\u0131klar\u0131 doldurulmam\u0131\u015f veya herhangi bir ba\u015flatma i\u015flemi yap\u0131lmam\u0131\u015ft\u0131r.<\/p>\n<\/li>\n
  2. \n
    \u00d6zelliklerin Doldurulmas\u0131 (Populating Properties\/Dependency Injection):<\/h3>\n
    Bean \u00f6rne\u011fi olu\u015fturulduktan sonra, Spring konteyneri, bean'in ihtiya\u00e7 duydu\u011fu t\u00fcm ba\u011f\u0131ml\u0131l\u0131klar\u0131 (di\u011fer bean'ler, yap\u0131land\u0131rma de\u011ferleri vb.) enjekte eder. Bu i\u015flem genellikle setter metotlar\u0131, kurucu metotlar veya alan enjeksiyonu (field injection) kullan\u0131larak ger\u00e7ekle\u015ftirilir. Bu, IoC prensibinin en belirgin \u015fekilde ortaya \u00e7\u0131kt\u0131\u011f\u0131 a\u015famad\u0131r.<\/p>\n
    \npackage com.example.service;\n\nimport org.springframework.beans.factory.annotation.Autowired;\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class MyDependentService {\n\n    private MyService myService;\n\n    public MyDependentService() {\n        System.out.println(\"1. MyDependentService bean'i yarat\u0131ld\u0131.\");\n    }\n\n    @Autowired\n    public void setMyService(MyService myService) {\n        this.myService = myService;\n        System.out.println(\"2. MyService ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 enjekte edildi.\");\n    }\n}\n        <\/pre>\n
    <\/code>\n    <\/li>\n
  3. \n
    'Aware' Aray\u00fczlerinin \u00c7a\u011fr\u0131lmas\u0131:<\/h3>\n
    E\u011fer bean, BeanNameAware<\/code>, BeanFactoryAware<\/code> veya ApplicationContextAware<\/code> gibi \"Aware\" aray\u00fczlerinden herhangi birini uyguluyorsa, Spring konteyneri ilgili metotlar\u0131 \u00e7a\u011f\u0131rarak bean'e kendi ad\u0131n\u0131, ba\u011fl\u0131 oldu\u011fu BeanFactory'yi veya ApplicationContext'i bildirir. Bu, bean'in kendi konteyneri hakk\u0131nda bilgi edinmesini sa\u011flar ve \u00e7ok \u00f6zel senaryolarda kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n
      \n
    • BeanNameAware.setBeanName()<\/code>: Bean'e kendi ad\u0131n\u0131 bildirir.<\/li>\n
    • BeanFactoryAware.setBeanFactory()<\/code>: Bean'e, onu olu\u015fturan BeanFactory'yi bildirir.<\/li>\n
    • ApplicationContextAware.setApplicationContext()<\/code>: Bean'e, onu i\u00e7eren ApplicationContext'i bildirir.<\/li>\n<\/ul>\n<\/li>\n
    • \n
      BeanPostProcessor (postProcessBeforeInitialization):<\/h3>\n
      Bu a\u015famada, bean'in kendi ba\u015flatma metotlar\u0131 (@PostConstruct<\/code>, InitializingBean.afterPropertiesSet()<\/code> veya \u00f6zel init-method<\/code>) \u00e7a\u011fr\u0131lmadan hemen \u00f6nce, t\u00fcm BeanPostProcessor<\/code>'lar postProcessBeforeInitialization()<\/code> metodunu \u00e7al\u0131\u015ft\u0131r\u0131r. Bu, Spring'in bean'ler \u00fczerinde ek i\u015flemler yapmas\u0131na veya onlar\u0131 sarmalamas\u0131na olanak tan\u0131r. \u00d6rne\u011fin, bean'i bir proxy ile de\u011fi\u015ftirmek veya \u00f6zel denetimler eklemek bu a\u015famada yap\u0131labilir.<\/p>\n<\/li>\n
    • \n
      Ba\u015flatma Geri \u00c7a\u011f\u0131rmalar\u0131 (Initialization Callbacks):<\/h3>\n
      Bu, bean'in kullan\u0131ma haz\u0131r hale getirilmesi i\u00e7in gerekli olan son ayarlamalar\u0131n yap\u0131ld\u0131\u011f\u0131 kritik a\u015famad\u0131r. Spring, a\u015fa\u011f\u0131daki s\u0131rayla ba\u015flatma metotlar\u0131n\u0131 \u00e7a\u011f\u0131r\u0131r:<\/p>\n
        \n
      1. @PostConstruct<\/code><\/strong>: JSR-250 standard\u0131na ait bu annotation ile i\u015faretlenmi\u015f metotlar \u00e7a\u011fr\u0131l\u0131r. En yayg\u0131n kullan\u0131lan ba\u015flatma y\u00f6ntemidir.<\/li>\n
      2. InitializingBean.afterPropertiesSet()<\/code><\/strong>: E\u011fer bean InitializingBean<\/code> aray\u00fcz\u00fcn\u00fc uyguluyorsa, bu metot \u00e7a\u011fr\u0131l\u0131r.<\/li>\n
      3. \u00d6zel init-method<\/code><\/strong>: E\u011fer bean tan\u0131m\u0131nda (XML veya Java Config) \u00f6zel bir \"init-method\" belirtilmi\u015fse, bu metot \u00e7a\u011fr\u0131l\u0131r.<\/li>\n<\/ol>\n
        Bu metotlar genellikle kaynaklar\u0131 y\u00fcklemek, \u00f6nbellekleri ba\u015flatmak veya di\u011fer karma\u015f\u0131k ba\u015flatma mant\u0131\u011f\u0131n\u0131 uygulamak i\u00e7in kullan\u0131l\u0131r. \u00d6rne\u011fin, bir veritaban\u0131 ba\u011flant\u0131 havuzunun ba\u015flang\u0131\u00e7 ayarlar\u0131 bu a\u015famada yap\u0131labilir.<\/p>\n<\/li>\n
      4. \n
        BeanPostProcessor (postProcessAfterInitialization):<\/h3>\n
        Ba\u015flatma geri \u00e7a\u011f\u0131rmalar\u0131 tamamland\u0131ktan hemen sonra, t\u00fcm BeanPostProcessor<\/code>'lar tekrar devreye girer ve postProcessAfterInitialization()<\/code> metodunu \u00e7al\u0131\u015ft\u0131r\u0131r. Bu, bean kullan\u0131ma sunulmadan \u00f6nce son bir de\u011fi\u015fiklik yapma veya bir proxy olu\u015fturma \u015fans\u0131 sunar. \u00d6zellikle Spring AOP (Aspect-Oriented Programming) ve di\u011fer geni\u015fletme mekanizmalar\u0131 bu noktada bean'lere m\u00fcdahale eder.<\/p>\n<\/li>\n
      5. \n
        Bean Kullan\u0131ma Haz\u0131r:<\/h3>\n
        T\u00fcm bu ad\u0131mlardan sonra, bean tamamen yap\u0131land\u0131r\u0131lm\u0131\u015f, ba\u015flat\u0131lm\u0131\u015f ve uygulaman\u0131z\u0131n di\u011fer bile\u015fenleri taraf\u0131ndan kullan\u0131lmaya haz\u0131rd\u0131r. Bean, Spring konteyneri taraf\u0131ndan y\u00f6netildi\u011fi s\u00fcrece bu durumda kal\u0131r ve t\u00fcm uygulama boyunca hizmet verir.<\/p>\n<\/li>\n
      6. \n
        Bean'in \u0130mha Edilmesi Geri \u00c7a\u011f\u0131rmalar\u0131 (Destruction Callbacks):<\/h3>\n
        Uygulama veya Spring konteyneri kapat\u0131ld\u0131\u011f\u0131nda, y\u00f6netilen bean'lerin kaynaklar\u0131n\u0131 d\u00fczg\u00fcn bir \u015fekilde serbest b\u0131rakmas\u0131 gerekir. Spring, a\u015fa\u011f\u0131daki s\u0131rayla imha metotlar\u0131n\u0131 \u00e7a\u011f\u0131r\u0131r:<\/p>\n
          \n
        1. @PreDestroy<\/code><\/strong>: JSR-250 standard\u0131na ait bu annotation ile i\u015faretlenmi\u015f metotlar \u00e7a\u011fr\u0131l\u0131r. En yayg\u0131n kullan\u0131lan imha y\u00f6ntemidir.<\/li>\n
        2. DisposableBean.destroy()<\/code><\/strong>: E\u011fer bean DisposableBean<\/code> aray\u00fcz\u00fcn\u00fc uyguluyorsa, bu metot \u00e7a\u011fr\u0131l\u0131r.<\/li>\n
        3. \u00d6zel destroy-method<\/code><\/strong>: E\u011fer bean tan\u0131m\u0131nda \u00f6zel bir \"destroy-method\" belirtilmi\u015fse, bu metot \u00e7a\u011fr\u0131l\u0131r.<\/li>\n<\/ol>\n
          Bu metotlar genellikle veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 kapatmak, dosya tan\u0131t\u0131c\u0131lar\u0131n\u0131 serbest b\u0131rakmak veya di\u011fer temizleme i\u015flemlerini ger\u00e7ekle\u015ftirmek i\u00e7in kullan\u0131l\u0131r. Kaynak s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nlemek i\u00e7in bu ad\u0131mlar\u0131n do\u011fru bir \u015fekilde uygulanmas\u0131 kritik \u00f6neme sahiptir.<\/p>\n<\/li>\n<\/ol>\n
          Bu ad\u0131mlar\u0131n tamam\u0131, Spring'in bean'ler \u00fczerinde tam kontrol sahibi olmas\u0131n\u0131 ve uygulamalar\u0131n\u0131z\u0131n tutarl\u0131 ve g\u00fcvenilir bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Her bir ad\u0131m, belirli bir amaca hizmet eder ve bean'in \u00f6mr\u00fc boyunca belirli davran\u0131\u015flar\u0131 enjekte etme veya \u00f6zelle\u015ftirme yetene\u011fi sunar.<\/p>\n
          Uygulamal\u0131 Senaryolar ve Geri \u00c7a\u011f\u0131rma Y\u00f6ntemleri: Hangi Se\u00e7ene\u011fi Ne Zaman Kullanmal\u0131?<\/h2>\n
          Spring'in bean ya\u015fam d\u00f6ng\u00fcs\u00fc, bir bean'in ba\u015flat\u0131lmas\u0131 ve yok edilmesi s\u0131ras\u0131nda belirli kodlar\u0131 \u00e7al\u0131\u015ft\u0131rman\u0131za olanak tan\u0131yan \u00e7e\u015fitli geri \u00e7a\u011f\u0131rma y\u00f6ntemleri sunar. Bu y\u00f6ntemleri do\u011fru bir \u015fekilde kullanmak, uygulama performans\u0131n\u0131 art\u0131rabilir, kaynak s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nleyebilir ve kodunuzun daha temiz olmas\u0131n\u0131 sa\u011flayabilir. Peki, hangi y\u00f6ntemi ne zaman tercih etmeliyiz? Bu b\u00f6l\u00fcmde, pop\u00fcler geri \u00e7a\u011f\u0131rma y\u00f6ntemlerini ve ger\u00e7ek d\u00fcnya senaryolar\u0131nda nas\u0131l kullan\u0131ld\u0131klar\u0131n\u0131 inceleyece\u011fiz.<\/p>\n
          Veritaban\u0131 Ba\u011flant\u0131 Y\u00f6neticisi \u00d6rne\u011fi<\/h3>\n
          Bir web uygulamas\u0131nda, veritaban\u0131 ba\u011flant\u0131 havuzlar\u0131n\u0131 y\u00f6netmek yayg\u0131n bir senaryodur. Bu havuzlar\u0131n uygulama ba\u015flad\u0131\u011f\u0131nda ba\u015flat\u0131lmas\u0131 ve uygulama kapan\u0131rken d\u00fczg\u00fcn bir \u015fekilde kapat\u0131lmas\u0131 gerekir. Aksi takdirde, a\u00e7\u0131k veritaban\u0131 ba\u011flant\u0131lar\u0131 veya bellek s\u0131z\u0131nt\u0131lar\u0131 ya\u015fanabilir. \u0130\u015fte bu durumda, Spring bean ya\u015fam d\u00f6ng\u00fcs\u00fc geri \u00e7a\u011f\u0131rmalar\u0131 devreye girer:<\/p>\n
          \npackage com.example.config;\n\nimport org.springframework.stereotype.Component;\nimport javax.annotation.PostConstruct;\nimport javax.annotation.PreDestroy;\n\n@Component\npublic class DatabaseConnectionManager {\n    private boolean connected;\n\n    public DatabaseConnectionManager() {\n        System.out.println(\"DatabaseConnectionManager: Kurucu metot \u00e7a\u011fr\u0131ld\u0131.\");\n    }\n\n    @PostConstruct\n    public void initConnectionPool() {\n        \/\/ Uygulama ba\u015flad\u0131\u011f\u0131nda bu metot \u00e7a\u011fr\u0131l\u0131r\n        System.out.println(\"DatabaseConnectionManager: @PostConstruct ile ba\u011flant\u0131 havuzu ba\u015flat\u0131l\u0131yor...\");\n        \/\/ Ger\u00e7ek bir senaryoda burada karma\u015f\u0131k JDBC veya JPA ba\u011flant\u0131 mant\u0131\u011f\u0131 uygulan\u0131r.\n        this.connected = true;\n        System.out.println(\"DatabaseConnectionManager: Veritaban\u0131na ba\u015far\u0131yla ba\u011flan\u0131ld\u0131.\");\n    }\n\n    public void executeQuery(String query) {\n        if (connected) {\n            System.out.println(\"DatabaseConnectionManager: '\" + query + \"' sorgusu \u00e7al\u0131\u015ft\u0131r\u0131l\u0131yor.\");\n        } else {\n            System.out.println(\"DatabaseConnectionManager: Ba\u011flant\u0131 kurulamad\u0131, sorgu \u00e7al\u0131\u015ft\u0131r\u0131lam\u0131yor.\");\n        }\n    }\n\n    @PreDestroy\n    public void destroyConnectionPool() {\n        \/\/ Uygulama kapan\u0131rken bu metot \u00e7a\u011fr\u0131l\u0131r\n        System.out.println(\"DatabaseConnectionManager: @PreDestroy ile ba\u011flant\u0131 havuzu kapat\u0131l\u0131yor...\");\n        \/\/ T\u00fcm a\u00e7\u0131k ba\u011flant\u0131lar burada serbest b\u0131rak\u0131l\u0131r, havuz kapat\u0131l\u0131r.\n        this.connected = false;\n        System.out.println(\"DatabaseConnectionManager: Veritaban\u0131 ba\u011flant\u0131s\u0131 kesildi.\");\n    }\n}\n<\/pre>\n
          <\/code><\/p>\n
          Yukar\u0131daki \u00f6rnekte @PostConstruct<\/code> annotation'\u0131, DatabaseConnectionManager<\/code> bean'inin t\u00fcm ba\u011f\u0131ml\u0131l\u0131klar\u0131 enjekte edildikten sonra (yani bean tamamen yap\u0131land\u0131r\u0131ld\u0131ktan sonra) initConnectionPool()<\/code> metodunun otomatik olarak \u00e7a\u011fr\u0131lmas\u0131n\u0131 sa\u011flar. Benzer \u015fekilde, @PreDestroy<\/code> annotation'\u0131, bean yok edilmeden hemen \u00f6nce destroyConnectionPool()<\/code> metodunun \u00e7a\u011fr\u0131lmas\u0131n\u0131 garanti eder. Bu sayede, veritaban\u0131 kaynaklar\u0131 uygulaman\u0131n \u00f6mr\u00fc boyunca d\u00fczg\u00fcn bir \u015fekilde y\u00f6netilir.<\/p>\n
          @PostConstruct<\/code> ve @PreDestroy<\/code> Kullan\u0131m\u0131<\/h3>\n
          Bu annotation'lar, Java EE (JSR-250) standard\u0131n\u0131n bir par\u00e7as\u0131d\u0131r ve Spring taraf\u0131ndan da desteklenir. Bean ya\u015fam d\u00f6ng\u00fcs\u00fc metodlar\u0131 i\u00e7in en modern ve \u00f6nerilen yakla\u015f\u0131md\u0131r. Neden mi?<\/p>\n
            \n
          • Standartla\u015fma:<\/strong> Sadece Spring'e \u00f6zg\u00fc de\u011fildir, di\u011fer Java EE konteynerlerinde de \u00e7al\u0131\u015f\u0131r.<\/li>\n
          • Okunabilirlik:<\/strong> Metodun amac\u0131n\u0131 do\u011frudan g\u00f6sterir, kodu daha anla\u015f\u0131l\u0131r k\u0131lar.<\/li>\n
          • Basitlik:<\/strong> \u00d6zel bir aray\u00fcz uygulamaya veya XML konfig\u00fcrasyonu yapmaya gerek kalmaz.<\/li>\n<\/ul>\n
            Genellikle ba\u015flatma i\u00e7in kaynak y\u00fckleme, \u00f6nbellek doldurma; imha i\u00e7in ise a\u00e7\u0131k kaynaklar\u0131 kapatma, kuyruklar\u0131 bo\u015faltma gibi i\u015flemlerde kullan\u0131l\u0131r. Bu annotation'lar, Spring'in annotation tabanl\u0131 konfig\u00fcrasyon yakla\u015f\u0131m\u0131n\u0131n ayr\u0131lmaz bir par\u00e7as\u0131d\u0131r ve geli\u015ftiricilere b\u00fcy\u00fck kolayl\u0131k sa\u011flar.<\/p>\n
            InitializingBean<\/code> ve DisposableBean<\/code> Aray\u00fczleri<\/h3>\n
            Spring'in kendi aray\u00fczleri olan InitializingBean<\/code> ve DisposableBean<\/code>, s\u0131ras\u0131yla afterPropertiesSet()<\/code> ve destroy()<\/code> metotlar\u0131n\u0131 i\u00e7erir. E\u011fer bir s\u0131n\u0131f bu aray\u00fczleri uyguluyorsa, Spring konteyneri bean olu\u015fturma ve yok etme s\u00fcrecinde bu metotlar\u0131 \u00e7a\u011f\u0131r\u0131r. Bu aray\u00fczleri kullanman\u0131n temel faydas\u0131, Spring'in \u00e7ekirdek mekanizmalar\u0131yla do\u011frudan etkile\u015fime ge\u00e7me imkan\u0131 sunmas\u0131d\u0131r.<\/p>\n
            \npackage com.example.service;\n\nimport org.springframework.beans.factory.DisposableBean;\nimport org.springframework.beans.factory.InitializingBean;\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class CustomLifecycleBean implements InitializingBean, DisposableBean {\n\n    public CustomLifecycleBean() {\n        System.out.println(\"CustomLifecycleBean: Kurucu metot \u00e7a\u011fr\u0131ld\u0131.\");\n    }\n\n    @Override\n    public void afterPropertiesSet() throws Exception {\n        System.out.println(\"CustomLifecycleBean: InitializingBean.afterPropertiesSet() \u00e7a\u011fr\u0131ld\u0131.\");\n        \/\/ Ba\u015flatma mant\u0131\u011f\u0131 buraya gelir, \u00f6rne\u011fin bir d\u0131\u015f servise ilk ba\u011flant\u0131y\u0131 kurma.\n    }\n\n    @Override\n    public void destroy() throws Exception {\n        System.out.println(\"CustomLifecycleBean: DisposableBean.destroy() \u00e7a\u011fr\u0131ld\u0131.\");\n        \/\/ \u0130mha mant\u0131\u011f\u0131 buraya gelir, \u00f6rne\u011fin a\u00e7\u0131lan t\u00fcm kaynaklar\u0131 serbest b\u0131rakma.\n    }\n}\n<\/pre>\n
            <\/code><\/p>\n
            Bu aray\u00fczler, @PostConstruct<\/code> ve @PreDestroy<\/code>'den daha eski bir yakla\u015f\u0131md\u0131r. G\u00fcn\u00fcm\u00fczde genellikle geriye d\u00f6n\u00fck uyumluluk veya belirli Spring internal bile\u015fenleri i\u00e7in kullan\u0131l\u0131r. Yeni projelerde genellikle annotation'lar tercih edilir \u00e7\u00fcnk\u00fc daha az ba\u011flay\u0131c\u0131d\u0131r ve kodun daha okunabilir olmas\u0131n\u0131 sa\u011flar.<\/p>\n
            \n    Uzman \u0130pucu: Kaynaklar\u0131n do\u011fru bir \u015fekilde serbest b\u0131rak\u0131ld\u0131\u011f\u0131ndan emin olmak i\u00e7in @PreDestroy<\/code> metodlar\u0131n\u0131zda veya DisposableBean.destroy()<\/code> uygulaman\u0131zda hata yakalama mekanizmalar\u0131 kullanmay\u0131 unutmay\u0131n. Beklenmedik durumlar, uygulaman\u0131n d\u00fczg\u00fcn kapanmas\u0131n\u0131 engelleyebilir.\n<\/div>\n
            BeanPostProcessor<\/code> ile Davran\u0131\u015flar\u0131 \u00d6zelle\u015ftirme<\/h3>\n
            BeanPostProcessor<\/code> aray\u00fcz\u00fc, Spring bean ya\u015fam d\u00f6ng\u00fcs\u00fcne derinlemesine m\u00fcdahale etmenizi sa\u011flar. T\u00fcm bean'ler ba\u015flat\u0131lmadan \u00f6nce ve sonra i\u015flem yapman\u0131za olanak tan\u0131r. Bu sayede, bean'lerin davran\u0131\u015flar\u0131n\u0131 de\u011fi\u015ftirebilir, onlar\u0131 vekil (proxy) objelerle sarmalayabilir veya ekstra konfig\u00fcrasyonlar ekleyebilirsiniz. \u00d6zellikle enjeksiyon, loglama, g\u00fcvenlik veya performans metrikleri gibi \u00e7apraz kesen endi\u015felerde (cross-cutting concerns) \u00e7ok g\u00fc\u00e7l\u00fcd\u00fcr.<\/p>\n
            \npackage com.example.processor;\n\nimport org.springframework.beans.BeansException;\nimport org.springframework.beans.factory.config.BeanPostProcessor;\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class AuditLogBeanPostProcessor implements BeanPostProcessor {\n\n    @Override\n    public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {\n        \/\/ System.out.println(\"AuditLogBeanPostProcessor: '\" + beanName + \"' bean'i ba\u015flat\u0131lmadan \u00f6nce i\u015flem g\u00f6r\u00fcyor.\");\n        return bean; \/\/ De\u011fi\u015fiklik yap\u0131lmazsa bean'i aynen geri d\u00f6nd\u00fcr.\n    }\n\n    @Override\n    public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {\n        if (beanName.equals(\"databaseConnectionManager\")) { \/\/ Belirli bir bean i\u00e7in \u00f6zelle\u015ftirme\n            System.out.println(\"AuditLogBeanPostProcessor: '\" + beanName + \"' bean'i ba\u015flat\u0131ld\u0131ktan sonra denetim kayd\u0131 eklendi.\");\n        }\n        return bean;\n    }\n}\n<\/pre>\n
            <\/code><\/p>\n
            Bu \u00f6rnekte, AuditLogBeanPostProcessor<\/code>, t\u00fcm bean'lerin ba\u015flat\u0131lma sonras\u0131 a\u015famas\u0131na m\u00fcdahale ederek belirli bir bean i\u00e7in bir denetim kayd\u0131 olu\u015fturabilir. Bu, sistem genelinde tutarl\u0131 bir davran\u0131\u015f sergilemek istedi\u011finiz durumlarda paha bi\u00e7ilmezdir. BeanPostProcessor<\/code>'lar, AOP (Aspect-Oriented Programming) gibi ileri d\u00fczey Spring \u00f6zelliklerinin temelini olu\u015fturur ve uygulaman\u0131n \u00e7ekirdek mant\u0131\u011f\u0131n\u0131 de\u011fi\u015ftirmeden ek davran\u0131\u015flar eklemenize olanak tan\u0131r.<\/p>\n
            \u0130leri D\u00fczey Konular ve En \u0130yi Uygulamalar: Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fcn\u00fc Optimize Etmek<\/h2>\n
            Spring Bean ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc temel d\u00fczeyde anlamak harika bir ba\u015flang\u0131\u00e7t\u0131r, ancak uygulaman\u0131z\u0131n performans\u0131n\u0131 ve y\u00f6netilebilirli\u011fini daha da art\u0131rmak i\u00e7in baz\u0131 ileri d\u00fczey konulara ve en iyi uygulamalara de\u011finmek \u00f6nemlidir. Bu b\u00f6l\u00fcmde, bean kapsamlar\u0131n\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fc \u00fczerindeki etkilerini, tembel ba\u015flatmay\u0131 (lazy initialization) ve karma\u015f\u0131k senaryolar i\u00e7in SmartLifecycle<\/code> gibi geli\u015fmi\u015f mekanizmalar\u0131 inceleyece\u011fiz.<\/p>\n
            Lazy Initialization ve Bean Kapsamlar\u0131<\/h3>\n
            Varsay\u0131lan olarak, Spring konteyneri uygulaman\u0131n ba\u015flat\u0131lmas\u0131 s\u0131ras\u0131nda t\u00fcm singleton bean'leri hemen olu\u015fturur ve ba\u015flat\u0131r. Bu durum, \u00f6zellikle \u00e7ok say\u0131da bean'i olan veya ba\u015flatma maliyeti y\u00fcksek olan uygulamalarda ba\u015flang\u0131\u00e7 s\u00fcresini uzatabilir. \u0130\u015fte bu noktada Lazy Initialization (Tembel Ba\u015flatma)<\/strong> devreye girer. Bir bean'i tembel olarak ba\u015flatmak, o bean'in yaln\u0131zca ilk kez ihtiya\u00e7 duyuldu\u011funda olu\u015fturulmas\u0131n\u0131 ve ba\u015flat\u0131lmas\u0131n\u0131 sa\u011flar. Bu, uygulaman\u0131z\u0131n ba\u015flang\u0131\u00e7 s\u00fcresini \u00f6nemli \u00f6l\u00e7\u00fcde h\u0131zland\u0131rabilir, ancak ilk eri\u015fim s\u0131ras\u0131nda gecikmeye neden olabilir.<\/p>\n
            Bir bean'i tembel olarak i\u015faretlemek i\u00e7in @Lazy<\/code> annotation'\u0131n\u0131 kullanabilirsiniz:<\/p>\n
            \npackage com.example.service;\n\nimport org.springframework.context.annotation.Lazy;\nimport org.springframework.stereotype.Service;\nimport javax.annotation.PostConstruct;\n\n@Service\n@Lazy\npublic class LazyLoadingService {\n    public LazyLoadingService() {\n        System.out.println(\"LazyLoadingService: Kurucu metot \u00e7a\u011fr\u0131ld\u0131 (Sadece ilk kullan\u0131mda!).\");\n    }\n\n    @PostConstruct\n    public void setup() {\n        System.out.println(\"LazyLoadingService: @PostConstruct metodu \u00e7al\u0131\u015ft\u0131 (Sadece ilk kullan\u0131mda!).\");\n    }\n\n    public String getGreeting() {\n        return \"Merhaba tembel y\u00fcklenmi\u015f servis!\";\n    }\n}\n<\/pre>\n
            <\/code><\/p>\n
            Bean'lerin kapsamlar\u0131 (scopes) da ya\u015fam d\u00f6ng\u00fclerini do\u011frudan etkiler:<\/p>\n
              \n
            • Singleton (Varsay\u0131lan):<\/strong> T\u00fcm uygulama boyunca tek bir \u00f6rnek olu\u015fturulur. Ya\u015fam d\u00f6ng\u00fcs\u00fc, uygulaman\u0131n ya\u015fam s\u00fcresiyle ayn\u0131d\u0131r. Uygulama ba\u015flat\u0131ld\u0131\u011f\u0131nda olu\u015fur, kapat\u0131ld\u0131\u011f\u0131nda yok edilir.<\/li>\n
            • Prototype:<\/strong> Her istek i\u00e7in yeni bir \u00f6rnek olu\u015fturulur. Spring, bu bean'i olu\u015fturur, yap\u0131land\u0131r\u0131r ve ba\u015flat\u0131r, ancak daha sonra onun ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc takip etmez. Bean'in imha edilmesi sorumlulu\u011fu geli\u015ftiriciye aittir. Bu, kaynak temizli\u011fi a\u00e7\u0131s\u0131ndan dikkatli olunmas\u0131 gerekti\u011fi anlam\u0131na gelir.<\/li>\n
            • Request\/Session\/Application (Web Kapsamlar\u0131):<\/strong> Bu kapsamlar yaln\u0131zca web uygulamalar\u0131nda ge\u00e7erlidir ve bean'in ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc belirli bir HTTP iste\u011fi, kullan\u0131c\u0131 oturumu veya web uygulamas\u0131 ba\u011flam\u0131yla s\u0131n\u0131rlar. \u00d6rne\u011fin, bir request-scoped bean, her HTTP iste\u011fi i\u00e7in olu\u015fturulur ve iste\u011fin sonunda yok edilir.<\/li>\n<\/ul>\n
              Do\u011fru kapsam\u0131 se\u00e7mek, bellek kullan\u0131m\u0131n\u0131 ve uygulama performans\u0131n\u0131 optimize etmek i\u00e7in \u00e7ok \u00f6nemlidir. Genellikle stateless (durumsuz) servisler i\u00e7in singleton, stateful (durumlu) ve her kullan\u0131mda yeni bir \u00f6rnek gerektiren nesneler i\u00e7in prototype tercih edilir. \u00d6zellikle prototype bean'lerde @PreDestroy<\/code> metotlar\u0131n\u0131n otomatik olarak \u00e7a\u011fr\u0131lmad\u0131\u011f\u0131n\u0131 unutmamak, kaynak s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nlemek i\u00e7in hayati \u00f6nem ta\u015f\u0131r.<\/p>\n
              BeanPostProcessor<\/code>'larla Davran\u0131\u015flar\u0131 Geni\u015fletmek<\/h3>\n
              BeanPostProcessor<\/code>'lar, tek tek bean'lerin \u00f6tesinde, t\u00fcm konteynerdeki bean'lerin ya\u015fam d\u00f6ng\u00fcs\u00fcne global d\u00fczeyde m\u00fcdahale etmek i\u00e7in g\u00fc\u00e7l\u00fc bir mekanizmad\u0131r. \u00d6rne\u011fin, uygulaman\u0131zdaki her servis bean'i i\u00e7in otomatik olarak loglama veya metrik toplama \u00f6zelli\u011fi eklemek istedi\u011finizi d\u00fc\u015f\u00fcn\u00fcn. Bunu her servise manuel olarak eklemek yerine, bir BeanPostProcessor<\/code> yazarak bu i\u015flemi otomatik hale getirebilirsiniz. Bu, AOP (Aspect-Oriented Programming) yakla\u015f\u0131mlar\u0131n\u0131n temelini olu\u015fturur ve kod tekrar\u0131n\u0131 azalt\u0131r.<\/p>\n
              \n\/\/ Custom BeanPostProcessor \u00d6rne\u011fi\nimport org.springframework.beans.BeansException;\nimport org.springframework.beans.factory.config.BeanPostProcessor;\nimport org.springframework.stereotype.Component;\n\n@Component\npublic class CustomBeanLifecycleLogger implements BeanPostProcessor {\n\n    @Override\n    public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {\n        \/\/ Geni\u015fletme mant\u0131\u011f\u0131: \u00d6rne\u011fin, belirli bir aray\u00fcz\u00fc uygulayan bean'lere \u00f6zel ayarlar yapmak.\n        \/\/ System.out.println(\"DEBUG: '\" + beanName + \"' bean'i ba\u015flat\u0131lmadan \u00f6nce i\u015flem g\u00f6r\u00fcyor.\");\n        return bean;\n    }\n\n    @Override\n    public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {\n        if (beanName.startsWith(\"my\")) { \/\/ \"my\" ile ba\u015flayan t\u00fcm bean'ler i\u00e7in loglama\n            System.out.println(\"DEBUG: '\" + beanName + \"' bean'i ba\u015flat\u0131ld\u0131ktan sonra denetim kayd\u0131 eklendi.\");\n        }\n        return bean;\n    }\n}\n<\/pre>\n
              <\/code><\/p>\n
              \n    Uzman \u0130pucu: B\u00fcy\u00fck ve karma\u015f\u0131k uygulamalarda, \u00f6zel BeanPostProcessor<\/code>'lar kullanarak \u00e7apraz kesen konular\u0131 (logging, g\u00fcvenlik, metrikler) merkezi bir yerden y\u00f6netebilirsiniz. Bu, kod tekrar\u0131n\u0131 \u00f6nler ve bak\u0131m kolayl\u0131\u011f\u0131 sa\u011flar, ayr\u0131ca Spring'in sa\u011flad\u0131\u011f\u0131 geni\u015fletilebilirlik noktalar\u0131ndan biridir.\n<\/div>\n
              SmartLifecycle<\/code> ile Daha Ak\u0131ll\u0131 Kontrol<\/h3>\n
              Standart ya\u015fam d\u00f6ng\u00fcs\u00fc geri \u00e7a\u011f\u0131rmalar\u0131 (@PostConstruct<\/code>, @PreDestroy<\/code>) \u00e7o\u011fu durumda yeterli olsa da, baz\u0131 geli\u015fmi\u015f senaryolarda daha fazla kontrol gerekebilir. \u00d6rne\u011fin, bir mesaj kuyru\u011fu dinleyicisi veya harici bir sistemle uzun s\u00fcreli ba\u011flant\u0131s\u0131 olan bir bean'in, uygulaman\u0131n ba\u015flat\u0131lmas\u0131 veya kapat\u0131lmas\u0131 s\u0131ras\u0131nda daha zarif bir \u015fekilde y\u00f6netilmesi gerekebilir. SmartLifecycle<\/code> aray\u00fcz\u00fc, bu t\u00fcr bile\u015fenler i\u00e7in daha ak\u0131ll\u0131 bir ba\u015flatma ve kapatma mekanizmas\u0131 sunar. Bu aray\u00fcz, bean'lerin ba\u015flatma ve durdurma i\u015flemlerini s\u0131ralaman\u0131za, hatta Spring konteynerinin ne zaman tamamen ba\u015flat\u0131l\u0131p durduruldu\u011funu takip etmenize olanak tan\u0131r. \u00d6zellikle mikroservis mimarilerinde veya kuyruk dinleyicileri gibi asenkron bile\u015fenlerde, sistemin sorunsuz bir \u015fekilde aya\u011fa kalkmas\u0131 ve kapanmas\u0131 i\u00e7in hayati \u00f6nem ta\u015f\u0131r. Bu sayede, uygulaman\u0131z\u0131n bile\u015fenleri aras\u0131nda koordineli bir ba\u015flatma ve durdurma s\u0131ras\u0131 belirleyebilir, beklenmedik veri kay\u0131plar\u0131n\u0131 veya tutars\u0131zl\u0131klar\u0131 \u00f6nleyebilirsiniz.<\/p>\n
              S\u0131k\u00e7a Sorulan Sorular ve Sonu\u00e7: Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fcne Hakimiyetin G\u00fcc\u00fc<\/h2>\n
              Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc, uygulamalar\u0131n\u0131z\u0131n \u00e7ekirde\u011finde yer alan ve performanstan kararl\u0131l\u0131\u011fa kadar bir\u00e7ok alan\u0131 etkileyen kritik bir konudur. Bu makale boyunca, bir bean'in do\u011fu\u015fundan yok olu\u015funa kadar ge\u00e7en her ad\u0131m\u0131, geri \u00e7a\u011f\u0131rma mekanizmalar\u0131n\u0131 ve ileri d\u00fczey ipu\u00e7lar\u0131n\u0131 ele ald\u0131k. G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, Spring konteyneri bean'lerimizi sadece olu\u015fturmakla kalmaz, ayn\u0131 zamanda onlar\u0131n t\u00fcm \u00f6m\u00fcrleri boyunca etkin bir \u015fekilde y\u00f6netilmesini sa\u011flar. Bu y\u00f6netim sayesinde, kaynak s\u0131z\u0131nt\u0131lar\u0131 gibi yayg\u0131n sorunlar\u0131n \u00f6n\u00fcne ge\u00e7ilir ve uygulaman\u0131z\u0131n daha g\u00fcvenilir \u00e7al\u0131\u015fmas\u0131 sa\u011flan\u0131r.<\/p>\n
              Mikroservislerde Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc Y\u00f6netimi: Vaka Analizi<\/h3>\n
              Bir mikroservis ortam\u0131nda, her servisin kendi ba\u011f\u0131ms\u0131z ya\u015fam d\u00f6ng\u00fcs\u00fc vard\u0131r. \u00d6rne\u011fin, bir \"Bildirim Servisi\" d\u00fc\u015f\u00fcnelim. Bu servis, bir mesaj kuyru\u011fundan (RabbitMQ, Kafka) bildirim mesajlar\u0131n\u0131 dinler. Servis ba\u015flad\u0131\u011f\u0131nda, mesaj dinleyicisinin ba\u015flat\u0131lmas\u0131, kuyruk ba\u011flant\u0131lar\u0131n\u0131n kurulmas\u0131 ve dinlemeye ba\u015flamas\u0131 gerekir. Bu, @PostConstruct<\/code> ile kolayca y\u00f6netilebilir. E\u011fer dinleyici d\u00fczg\u00fcn bir \u015fekilde ba\u015flat\u0131lmazsa, bildirimler i\u015flenmez ve kullan\u0131c\u0131lar bilgilendirilmez. \u00d6te yandan, servis kapat\u0131ld\u0131\u011f\u0131nda, a\u00e7\u0131k kuyruk ba\u011flant\u0131lar\u0131n\u0131n g\u00fcvenli bir \u015fekilde kapat\u0131lmas\u0131 ve dinleyicinin durdurulmas\u0131 esast\u0131r. Aksi takdirde, kuyrukta i\u015flenmemi\u015f mesajlar kalabilir veya kaynak s\u0131z\u0131nt\u0131lar\u0131 ya\u015fanabilir. \u0130\u015fte @PreDestroy<\/code> veya SmartLifecycle<\/code> gibi mekanizmalar, bu t\u00fcr senaryolarda hizmetin zarif bir \u015fekilde kapanmas\u0131n\u0131 sa\u011flayarak veri kayb\u0131n\u0131 ve sistem tutars\u0131zl\u0131klar\u0131n\u0131 \u00f6nler. Mikroservisler aras\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131n ve veri ak\u0131\u015f\u0131n\u0131n karma\u015f\u0131k oldu\u011fu bir ortamda, her servisin kendi ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc kusursuz y\u00f6netmesi, t\u00fcm sistemin genel istikrar\u0131 i\u00e7in hayati \u00f6nem ta\u015f\u0131r. Do\u011fru ya\u015fam d\u00f6ng\u00fcs\u00fc y\u00f6netimi, mikroservislerin esnekli\u011fini ve dayan\u0131kl\u0131l\u0131\u011f\u0131n\u0131 art\u0131r\u0131r.<\/p>\n
              S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n
                \n
              1. \n        @PostConstruct<\/code> ve InitializingBean<\/code> aras\u0131ndaki fark nedir?<\/strong><\/p>\n
                @PostConstruct<\/code>, JSR-250 standard\u0131n\u0131n bir par\u00e7as\u0131d\u0131r ve Spring'e \u00f6zg\u00fc de\u011fildir; bu nedenle di\u011fer Java EE konteynerlerinde de \u00e7al\u0131\u015fabilir. Kodun daha temiz ve okunakl\u0131 olmas\u0131n\u0131 sa\u011flar. InitializingBean<\/code> ise Spring'in kendi aray\u00fcz\u00fcd\u00fcr ve afterPropertiesSet()<\/code> metodunu i\u00e7erir. Genel olarak, modern Spring uygulamalar\u0131nda @PostConstruct<\/code> tercih edilir, \u00e7\u00fcnk\u00fc standart bir yakla\u015f\u0131md\u0131r ve aray\u00fcz uygulamas\u0131 gerektirmez, b\u00f6ylece kodunuzu Spring'e daha az ba\u011f\u0131ml\u0131 hale getirir.<\/p>\n<\/li>\n
              2. \n        Bean kapsamlar\u0131 ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc nas\u0131l etkiler?<\/strong><\/p>\n
                Singleton<\/code> bean'ler, uygulama ya\u015fam d\u00f6ng\u00fcs\u00fcyle ayn\u0131 \u00f6mre sahiptir; uygulama ba\u015flad\u0131\u011f\u0131nda olu\u015fturulur ve kapat\u0131ld\u0131\u011f\u0131nda yok edilir. Prototype<\/code> bean'ler ise her talep edildi\u011finde yeni bir \u00f6rnek olarak olu\u015fturulur ve Spring bu bean'i ba\u015flatt\u0131ktan sonra ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc y\u00f6netmeyi b\u0131rak\u0131r. Yani prototype<\/code> bean'ler i\u00e7in destroy<\/code> metotlar\u0131 Spring taraf\u0131ndan otomatik olarak \u00e7a\u011fr\u0131lmaz; kaynak temizli\u011fi geli\u015ftiricinin sorumlulu\u011fundad\u0131r. Web kapsamlar\u0131 (request<\/code>, session<\/code> gibi) ise bean'in \u00f6mr\u00fcn\u00fc ilgili web ba\u011flam\u0131yla s\u0131n\u0131rlar ve bu ba\u011flam sona erdi\u011finde bean yok edilir.<\/p>\n<\/li>\n
              3. \n        Spring uygulamas\u0131n\u0131 durdurdu\u011fumda destroy<\/code> metodu her zaman \u00e7a\u011fr\u0131l\u0131r m\u0131?<\/strong><\/p>\n
                Singleton<\/code> kapsam\u0131ndaki bean'ler i\u00e7in Spring konteyneri d\u00fczg\u00fcn bir \u015fekilde kapat\u0131ld\u0131\u011f\u0131nda (\u00f6rne\u011fin, web uygulamas\u0131n\u0131n durdurulmas\u0131 veya ApplicationContext.close()<\/code> \u00e7a\u011fr\u0131lmas\u0131yla), destroy<\/code> metotlar\u0131 (@PreDestroy<\/code>, DisposableBean.destroy()<\/code> veya \u00f6zel destroy-method<\/code>) \u00e7a\u011fr\u0131l\u0131r. Ancak prototype<\/code> kapsam\u0131ndaki bean'ler i\u00e7in Spring, bu metotlar\u0131 otomatik olarak \u00e7a\u011f\u0131rmaz; bean'in yok edilmesi ve kaynak temizli\u011fi geli\u015ftiricinin sorumlulu\u011fundad\u0131r. Bu nedenle, prototype<\/code> bean'lerde kaynak y\u00f6netimine \u00f6zellikle dikkat etmek gerekir.<\/p>\n<\/li>\n<\/ol>\n
                Bu makale, Spring Bean Ya\u015fam D\u00f6ng\u00fcs\u00fc hakk\u0131nda kapsaml\u0131 bir rehber sunarak, bu karma\u015f\u0131k ancak temel konuyu ad\u0131m ad\u0131m anlaman\u0131za yard\u0131mc\u0131 olmay\u0131 hedefledi. Bean'lerin nas\u0131l olu\u015fturuldu\u011funu, yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131n\u0131, kullan\u0131ld\u0131\u011f\u0131n\u0131 ve yok edildi\u011fini bilmek, daha sa\u011flam, bak\u0131m\u0131 kolay ve performansl\u0131 Spring uygulamalar\u0131 geli\u015ftirmenizin temelini olu\u015fturur. Art\u0131k bu bilgilere sahip oldu\u011funuza g\u00f6re, Spring uygulamalar\u0131n\u0131zdaki bean'leri daha bilin\u00e7li bir \u015fekilde y\u00f6netebilir ve olas\u0131 sorunlar\u0131n \u00f6n\u00fcne ge\u00e7ebilirsiniz. Unutmay\u0131n, iyi bir Spring geli\u015ftiricisi olman\u0131n yolu, framework'\u00fcn temel prensiplerini derinlemesine anlamaktan ge\u00e7er.<\/p>\n