<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Self-Hosted on Erkid Hoxholli</title>
    <link>https://erkidhoxholli.gitlab.io/tags/self-hosted/</link>
    <description>Recent content in Self-Hosted on Erkid Hoxholli</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://erkidhoxholli.gitlab.io/tags/self-hosted/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preparing a Codebase for Horizontal Scalability (On-Premises / Self-Hosted)</title>
      <link>https://erkidhoxholli.gitlab.io/posts/preparing-codebase-for-horizontal-scalability/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://erkidhoxholli.gitlab.io/posts/preparing-codebase-for-horizontal-scalability/</guid>
      <description>&lt;p&gt;Many early-stage startups and solo developers begin with a classic, streamlined stack: a &lt;strong&gt;React SPA frontend&lt;/strong&gt;, a single &lt;strong&gt;Node.js REST API&lt;/strong&gt;, a single &lt;strong&gt;database instance&lt;/strong&gt;, and &lt;strong&gt;Caddy&lt;/strong&gt; acting as a reverse proxy and SSL terminator.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;A Note on Cloud vs. On-Premises:&lt;/strong&gt;&lt;br&gt;&#xA;If you run on managed hyperscalers (AWS, GCP, Azure), much of horizontal scaling is abstracted away behind managed services: AWS Application Load Balancers (ALB), CloudFront, ElastiCache, and Amazon RDS with built-in connection proxies and read replicas.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
