<?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 Amfelt</title><link>https://amfelt.com/tags/architecture/</link><description>Recent content in Architecture on Amfelt</description><generator>Hugo</generator><language>en-us</language><copyright>© 2026 Amfelt Labs B.V.</copyright><lastBuildDate>Sun, 01 Nov 2026 00:08:00 +0000</lastBuildDate><atom:link href="https://amfelt.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>We chose HTMX over React for our app</title><link>https://amfelt.com/blog/htmx-instead-of-react/</link><pubDate>Sun, 01 Nov 2026 00:08:00 +0000</pubDate><guid>https://amfelt.com/blog/htmx-instead-of-react/</guid><description>Why a team with Go and Hugo experience built a CRUD-shaped control plane from server-rendered HTML fragments instead of React, what that costs us, and the kind of app where we would choose differently.</description></item><item><title>We skipped microservices and built a modular monolith</title><link>https://amfelt.com/blog/why-our-platform-is-a-modular-monolith/</link><pubDate>Sun, 01 Nov 2026 00:07:00 +0000</pubDate><guid>https://amfelt.com/blog/why-our-platform-is-a-modular-monolith/</guid><description>Why a small team with a fixed stack chose one Go binary per app on one Postgres instead of microservices, what that costs, and the triggers that would make us split.</description></item><item><title>Keep the site static, put a Go server in front of it</title><link>https://amfelt.com/blog/gating-a-static-site-with-go/</link><pubDate>Sun, 01 Nov 2026 00:06:00 +0000</pubDate><guid>https://amfelt.com/blog/gating-a-static-site-with-go/</guid><description>How we gave a Hugo site per-user access control without giving up static output: a small Gin server, Hanko for sign-in, and the whole site embedded in the binary.</description></item></channel></rss>