<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>architecture on Raighne&#39;s Blog</title>
    <link>/tags/architecture/</link>
    <description>Recent content in architecture on Raighne&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 12 Apr 2026 10:36:01 +0800</lastBuildDate><atom:link href="/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop Making Your Microservices Aggregate Each Other&#39;s Data</title>
      <link>/posts/backend_composition_layer/</link>
      <pubDate>Sun, 12 Apr 2026 10:36:01 +0800</pubDate>
      
      <guid>/posts/backend_composition_layer/</guid>
      <description>How It Started A few months ago, I was reviewing the dependency graph of one of our infrastructure services — an Auth service responsible for session and identity. Something looked off. This service, whose job was to manage authentication, was making outbound calls to four downstream domain services: user profiles, billing, messaging, and a core platform API.
An auth service calling a billing service? That&amp;rsquo;s not authentication. That&amp;rsquo;s aggregation.
I pulled the thread.</description>
    </item>
    
  </channel>
</rss>
