<?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 Johan Basson</title>
    <link>https://johanbasson.net/tags/clean-architecture/</link>
    <description>Recent content in Clean-Architecture on Johan Basson</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://johanbasson.net/tags/clean-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an API from the Domain Outwards</title>
      <link>https://johanbasson.net/posts/build-api-from-domain-outwards/</link>
      <pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://johanbasson.net/posts/build-api-from-domain-outwards/</guid>
      <description>&lt;p&gt;When building backend services, it is very easy to start with the framework.&lt;/p&gt;
&lt;p&gt;Create the controller.&lt;/p&gt;
&lt;p&gt;Generate the database entity.&lt;/p&gt;
&lt;p&gt;Add the repository.&lt;/p&gt;
&lt;p&gt;Then somewhere between HTTP requests and database tables, try to find a place where the business logic fits.&lt;/p&gt;
&lt;p&gt;I have built many systems this way.&lt;/p&gt;
&lt;p&gt;It works.&lt;/p&gt;
&lt;p&gt;Until it doesn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;Over time I have started moving in the opposite direction:&lt;/p&gt;
&lt;p&gt;Start with the domain.&lt;/p&gt;
&lt;p&gt;Everything else is just an adapter.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
