<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>vps on Mr. Buch</title><link>https://mrbu.ch/tags/vps/</link><description>Recent content in vps on Mr. Buch</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>c@mrbu.ch (Chintan Buch)</managingEditor><webMaster>c@mrbu.ch (Chintan Buch)</webMaster><copyright>© 2026 Chintan Buch</copyright><lastBuildDate>Tue, 16 Jun 2026 00:15:00 +0530</lastBuildDate><atom:link href="https://mrbu.ch/tags/vps/index.xml" rel="self" type="application/rss+xml"/><item><title>The Invisible Backend: A Pattern for Bootstrapped Infrastructure</title><link>https://mrbu.ch/articles/invisible-backend-pattern/</link><pubDate>Tue, 16 Jun 2026 00:15:00 +0530</pubDate><author>c@mrbu.ch (Chintan Buch)</author><guid>https://mrbu.ch/articles/invisible-backend-pattern/</guid><description>&lt;p&gt;You start your startup with one backend service. Simple, lean, single VPS. Works great. But as your product grows, you add more: a caching layer to speed up reads, a message queue to handle async jobs, maybe a microservice to offload payments or image processing. Suddenly you&amp;rsquo;re running five services on one box.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://mrbu.ch/articles/invisible-backend-pattern/cover.jpg"/></item></channel></rss>