<?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 Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/architecture/</link>
    <description>Recent content in Architecture on Robert Terakedis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2020 Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.terakedis.dev/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSO Is Not a Flip Switch</title>
      <link>https://blog.terakedis.dev/post/sso-is-not-a-flip-switch/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/sso-is-not-a-flip-switch/</guid>
      <description>
        
          
            &lt;p&gt;When we started modernizing the LMS infrastructure, the first thing someone asked was: &amp;quot;Can we just add SSO to the LMS?&amp;quot;&lt;/p&gt;
&lt;p&gt;It&#39;s a reasonable question. It sounds like a small ask — flip a switch, wire up a login button, done. But the moment you start pulling on that thread, you find out it&#39;s not a switch at all. It&#39;s a decision about where identity lives across every system you own, and getting it wrong means you end up with the same mess you started with, just with a single sign-on button in front of it.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>How to host blog images for free with Backblaze B2 and Cloudflare</title>
      <link>https://blog.terakedis.dev/post/b2-cloudflare-image-hosting/</link>
      <pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/b2-cloudflare-image-hosting/</guid>
      <description>
        
          
            &lt;p&gt;When I migrated this blog to Hugo, I had to figure out where images would live. My original thought was simple enough: store them in the GitHub repo. That worked fine for six months. Then I started thinking about what happens when I have hundreds of posts with images, and the repo turns into a photo dump.&lt;/p&gt;
&lt;p&gt;I looked at Cloudflare Images next. It seemed obvious—I&#39;m already paying for Cloudflare for DNS and SSL. But the pricing pushed me away: the transform API costs add up if you&#39;re generating variants (WebP, different sizes), and I&#39;d be locking myself into Cloudflare&#39;s image manipulation if I ever wanted to migrate. That didn&#39;t feel like room to grow.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>