<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hexagonal Architecture on Victor Laurance - Software Engineer</title><link>https://laurance.dev/en/tags/hexagonal-architecture/</link><description>Recent content in Hexagonal Architecture on Victor Laurance - Software Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://laurance.dev/en/tags/hexagonal-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Applying Hexagonal Architecture in a Spring Boot Application</title><link>https://laurance.dev/en/blog/hexagonal-architecture/</link><pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate><guid>https://laurance.dev/en/blog/hexagonal-architecture/</guid><description>&lt;p>If you have maintained a Spring Boot application long enough, you have probably seen business rules, controllers, and JPA entities all mixed up in the exact same place. It works—until the day you need to replace the database, write decent unit tests, or simply understand where business logic ends and the framework begins. That exact pain led me to study Hexagonal Architecture in depth, and in this article, I want to show how I applied these concepts in a real-world Spring Boot application.&lt;/p></description></item></channel></rss>