<?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>Architecture on Momo Engineering Journal</title><link>/tags/architecture/</link><description>Recent content in Architecture on Momo Engineering Journal</description><image><title>Momo Engineering Journal</title><url>/images/og-image.png</url><link>/images/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2026 02:07:10 -0600</lastBuildDate><atom:link href="/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Seams, Not Plugins: A Fast Path That Stays Concrete</title><link>/posts/044-plugin-seam-architecture/</link><pubDate>Wed, 26 Aug 2026 16:45:18 +0000</pubDate><guid>/posts/044-plugin-seam-architecture/</guid><description>Adaptive behaviors use compile-time Go interface seams injected at decision points — not dynamic plugins. The fast path stays concrete; the trust core stays auditable; policy is declarative.</description></item><item><title>Replication Strategies and the Polymorphic Engine</title><link>/posts/002-replication-strategies-polymorphic/</link><pubDate>Mon, 04 May 2026 18:54:37 +0000</pubDate><guid>/posts/002-replication-strategies-polymorphic/</guid><description>Chain, Splay, and Primary-Splay replication — and the metrics-driven controller that switches between them at runtime.</description></item><item><title>Origin: From Replication Playground to Object Store</title><link>/posts/001-origin-and-genesis/</link><pubDate>Tue, 09 Sep 2025 20:10:05 +0000</pubDate><guid>/posts/001-origin-and-genesis/</guid><description>How momo started as a file-replication playground in Go and grew into a distributed content-addressed object store.</description></item></channel></rss>