<?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>Review on Patryk Bandurski</title>
    <link>https://ambassadorpatryk.com/categories/review/</link>
    <description>Recent content in Review on Patryk Bandurski</description>
    <image>
      <title>Patryk Bandurski</title>
      <url>https://ambassadorpatryk.com/images/patryk-og.png</url>
      <link>https://ambassadorpatryk.com/images/patryk-og.png</link>
    </image>
    <generator>Hugo -- 0.160.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ambassadorpatryk.com/categories/review/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Integration Architecture Starts Where System Architecture Ends</title>
      <link>https://ambassadorpatryk.com/posts/integration-architecture-starts-where-system-ends/</link>
      <pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://ambassadorpatryk.com/posts/integration-architecture-starts-where-system-ends/</guid>
      <description>&lt;p&gt;When I think about integration, I naturally zoom in — APIs, flows, transformations, connectors. That&amp;rsquo;s the world I live in daily as an integration architect. A recent training made me realize I&amp;rsquo;ve been solving the right problems at the wrong level.&lt;/p&gt;
&lt;p&gt;The course &amp;ldquo;Strategic Integration Design with DDD&amp;rdquo; by Karol Skrzymowski and Philipp Kostyra introduced me to a perspective I hadn&amp;rsquo;t fully articulated before: integration architecture is not system architecture. It&amp;rsquo;s ecosystem architecture. And that distinction changes everything.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
