<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reference Architecture on Tracy Bannon</title>
    <link>/tags/reference-architecture/</link>
    <description>Recent content in Reference Architecture on Tracy Bannon</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 30 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="/tags/reference-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>This Reference Architecture is No Good --&gt; What is an RA?</title>
      <link>/post/2023/2023-07-30-whyreferencearchitectures/</link>
      <pubDate>Sun, 30 Jul 2023 00:00:00 +0000</pubDate>
      
      <guid>/post/2023/2023-07-30-whyreferencearchitectures/</guid>
      <description>𝗧𝗵𝗶𝘀 𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗶𝘀 𝗻𝗼 𝗴𝗼𝗼𝗱! It’s missing the list of technology to use and how to knit them together.  I heard this recently and became very aware that I needed to do a bit more mentoring on software architecture and in particular, reference architectures. Here’s the 411: A software reference architecture is a common abstraction or standardization of design that can be reused. Abstraction is the key and it serves as a guide for designing and building software systems in a particular domain.</description>
    </item>
    
  </channel>
</rss>
