<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Enterprise-Integration on Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/enterprise-integration/</link>
    <description>Recent content in Enterprise-Integration 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/enterprise-integration/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>The $300K Spreadsheet: How Manual Provisioning Became a Liability</title>
      <link>https://blog.terakedis.dev/post/the-300k-spreadsheet/</link>
      <pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/the-300k-spreadsheet/</guid>
      <description>
        
          
            &lt;p&gt;Last year I got pulled into a project where the team was drowning in spreadsheets. Not the good kind, but rather the unfortunate kind: manual user provisioning lists, copy-paste operations between systems, and a recurring cloud bill that kept climbing because of over-provisioned resources sitting idle.&lt;/p&gt;
&lt;p&gt;The kicker? Along with all the manual inefficiences, we incurred $300,000/year in overprovisioned cloud spend. And that was before we even talked about the staff time or the risk of things breaking when a step in the process was missed.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>