<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>/adgadev/</title>
    <link>https://adgadev.com/</link>
    <description>Recent content on /adgadev/</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 26 Aug 2022 18:00:00 +0000</lastBuildDate><atom:link href="https://adgadev.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Extending and customizing auto-configuration classes provided by Spring Boot</title>
      <link>https://adgadev.com/customizing-spring-boot-autoconfigurations/</link>
      <pubDate>Fri, 26 Aug 2022 18:00:00 +0000</pubDate>
      
      <guid>https://adgadev.com/customizing-spring-boot-autoconfigurations/</guid>
      <description>Problem statement Imagine a scenario when we need to enable certain spring boot auto-configuration on a subset of environments only. The reason for that may be that i.e. our new feature will use new database (mongo) which hasn’t been setup on all environments yet for some reason, but we don’t want this issue to stop us from deploying new version of the application.
 Not all spring boot auto-configurations support disabling them using property.</description>
    </item>
    
    <item>
      <title>Finding origin and context of JPA issued SQL statements</title>
      <link>https://adgadev.com/finding-origin-and-context-of-jpa-issued-sql-statemets/</link>
      <pubDate>Wed, 02 Dec 2020 20:00:00 +0000</pubDate>
      
      <guid>https://adgadev.com/finding-origin-and-context-of-jpa-issued-sql-statemets/</guid>
      <description>What problem are we solving here? ORM frameworks like Hibernate and other JPA implementors can significantly simplify development of persistence layer. Introducing entity abstraction level helps to model clean business domain and to hide underlying SQL statements used to achieve persistence of the domain. Such approach is especially useful in large domains, since developer no longer needs to create and maintain all SQL statements used by application. Just a few JPA annotations like @Entity / @ManyToOne / @OneToMany etc.</description>
    </item>
    
    <item>
      <title></title>
      <link>https://adgadev.com/search/placeholder/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://adgadev.com/search/placeholder/</guid>
      <description></description>
    </item>
    
    <item>
      <title></title>
      <link>https://adgadev.com/top/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://adgadev.com/top/about/</guid>
      <description>I&amp;rsquo;m a software engineer with more than 12 years of experience building enterprise applications across multiple industries. My main field of expertise is backend development, primarily using Java and its ecosystem like Spring / Hibernate / JEE. Enthusiast of Spring / Spring Boot technology stack, microservices, Domain Driven Design and clean code principles.
I&amp;rsquo;m passionate about all aspects of software engineering, looks for pure and possibly new solutions and eager to learn.</description>
    </item>
    
  </channel>
</rss>
