<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Spring on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/spring/</link>
		<description>Recent content in Spring on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Jul 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/spring/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Spring Boot Dependency Injection Without Losing Your Architecture</title>
				<link>https://dplabs.tech/blog/spring-boot-dependency-injection/</link>
				<pubDate>Mon, 21 Jul 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/spring-boot-dependency-injection/</guid>
				<description>&lt;p&gt;Spring&amp;rsquo;s dependency injection container is one of the most mature and capable DI frameworks available. It&amp;rsquo;s also capable of enabling architectures that are deeply coupled to Spring internals, impossible to test without a full Spring context, and opaque about their dependencies.&lt;/p&gt;&#xA;&lt;p&gt;The patterns that produce good Spring Boot architectures are not complicated. They require deliberate choices about when to use Spring and when to step back from it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;constructor-injection-is-non-negotiable&#34;&gt;Constructor Injection Is Non-Negotiable&lt;/h2&gt;&#xA;&lt;p&gt;Spring supports three injection mechanisms: constructor, setter, and field injection. Field injection (&lt;code&gt;@Autowired&lt;/code&gt; on a field) is the most common and the worst.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Modern Spring Boot Architecture: Beyond the Three-Layer Application</title>
				<link>https://dplabs.tech/blog/modern-spring-boot-architecture/</link>
				<pubDate>Mon, 02 Dec 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/modern-spring-boot-architecture/</guid>
				<description>&lt;p&gt;The three-layer architecture — controllers, services, repositories — is how most Spring Boot tutorials present application structure. It&amp;rsquo;s a reasonable starting point. It&amp;rsquo;s also a pattern that breaks down as applications grow.&lt;/p&gt;&#xA;&lt;p&gt;The problems are predictable: services become God classes with hundreds of methods, repository calls leak into controllers, domain logic spreads across multiple layers, and changing anything requires understanding the entire application at once. The layered architecture doesn&amp;rsquo;t enforce boundaries — it suggests them. Suggestions decay under deadline pressure.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
