<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microservices on Tracy Bannon</title>
    <link>/tags/microservices/</link>
    <description>Recent content in Microservices on Tracy Bannon</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Mar 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forget monoliths vs. microservices. Cognitive load is what matters.</title>
      <link>/post/2022/2022-03-22-cognitiveload/</link>
      <pubDate>Tue, 22 Mar 2022 00:00:00 +0000</pubDate>
      
      <guid>/post/2022/2022-03-22-cognitiveload/</guid>
      <description>“Forget monoliths vs. microservices. Cognitive load is what matters.” - Skelton &amp;amp; Pais.
I’ve argued for nearly 10 years that Microservice patterns can be overwhelming and when coupled with the explosion in open source, can lead to dramatic cognitive overload. Cognitive load/overload has a very measurable impact on software developers and delivery teams. In researching ways to detect and address this challenge, I came across a very common sense, and thought provoking article.</description>
    </item>
    
  </channel>
</rss>
