<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps on scarbrough.co.uk</title>
    <link>/tags/devops/</link>
    <description>Recent content in DevOps on scarbrough.co.uk</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 28 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>On-premise or not?</title>
      <link>/post/on-premise-or-not/</link>
      <pubDate>Sun, 28 Sep 2025 00:00:00 +0000</pubDate>
      <guid>/post/on-premise-or-not/</guid>
      <description>Azure Local was mentioned in a discussion with a few other engineers, the other month. I&amp;rsquo;d never heard of it, but I could guess it had something to do with running an on-premise instance of Azure. Apparently they&amp;rsquo;re calling it &amp;rsquo;edge computing&#39;.&#xA;There&amp;rsquo;s a list of things we don&amp;rsquo;t want migrated to Azure, when we think about it, such as security camera streaming and recording, database for the security cards, software-defined networking, internal hostname resolution, that sort of thing.</description>
    </item>
    <item>
      <title>Azure Resource Group Security and Authentication</title>
      <link>/post/security/resource-group-security/</link>
      <pubDate>Wed, 31 Jan 2024 00:00:00 +0000</pubDate>
      <guid>/post/security/resource-group-security/</guid>
      <description>The security configuration of Azure services is a fairly broad subject area, and this is more of an introduction to how it works for a Resource Group, in the context of a Logic App that needs to interact with multiple resources. If a DevOps team, instead of the developers, is managing the security, a considerable amount of time will be spent planning and designing services beforehand, and later trying to figure out which security configurations are preventing the services working.</description>
    </item>
    <item>
      <title>Why &#39;low code&#39; isn&#39;t always better</title>
      <link>/post/development/low-code-development/</link>
      <pubDate>Sat, 20 Jan 2024 00:00:00 +0000</pubDate>
      <guid>/post/development/low-code-development/</guid>
      <description>One of the most important lessons I&amp;rsquo;d learned from working with Azure, over the last year or so, is that careful thought should be given to whether it&amp;rsquo;s better to implement a service as a &amp;rsquo;low code&amp;rsquo; solution, or as conventionally-developed software. The former isn&amp;rsquo;t always the fastest, cheapest or more efficient way to get something deployed.&#xA;I&amp;rsquo;m currently of the opinion that Azure&amp;rsquo;s Logic App system is quite good for integrations and basic scheduled tasks - and it has indeed made those kind of things easier to manage - and there aren&amp;rsquo;t any convoluted deployment pipelines to bother with.</description>
    </item>
  </channel>
</rss>
