<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Clean Architecture on Gürkan UÇAR</title>
    <link>https://gurkanucar.com/tags/clean-architecture/</link>
    <description>Recent content in Clean Architecture on Gürkan UÇAR</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 08 Aug 2026 10:00:00 +0300</lastBuildDate>
    <atom:link href="https://gurkanucar.com/tags/clean-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Adapter and Strategy: Keeping External Services Outside the Domain</title>
      <link>https://gurkanucar.com/posts/clean-architecture-adapter-and-strategy-spring-boot/</link>
      <pubDate>Sat, 08 Aug 2026 10:00:00 +0300</pubDate>
      <guid>https://gurkanucar.com/posts/clean-architecture-adapter-and-strategy-spring-boot/</guid>
      <description>Two different external companies, two incompatible APIs, one domain model. The Adapter pattern gives them a common language in Spring Boot, while Strategy decides which one should run: at startup with @ConditionalOnProperty or per request with a factory.</description>
    </item>
    <item>
      <title>Chain of Responsibility: Turning Complex Rules Into a Pipeline</title>
      <link>https://gurkanucar.com/posts/chain-of-responsibility-spring-boot/</link>
      <pubDate>Sat, 08 Aug 2026 10:00:00 +0300</pubDate>
      <guid>https://gurkanucar.com/posts/chain-of-responsibility-spring-boot/</guid>
      <description>Instead of managing many business rules in one service, use Chain of Responsibility and a pipeline to make the rules independent, testable and easy to extend.</description>
    </item>
    <item>
      <title>Facade Pattern: Hiding Complex Subsystems Behind One Door</title>
      <link>https://gurkanucar.com/posts/facade-pattern-spring-boot/</link>
      <pubDate>Sat, 08 Aug 2026 10:00:00 +0300</pubDate>
      <guid>https://gurkanucar.com/posts/facade-pattern-spring-boot/</guid>
      <description>Instead of dealing with payment, ticketing, baggage, notification and loyalty systems one by one in a booking flow, the Facade Pattern puts the whole workflow behind a single interface.</description>
    </item>
  </channel>
</rss>
