🔧 From Observability To Architectural Observability — Shifting Left for Resiliency

In my previous article, Managing Architectural Tech Debt, I talked about understanding and managing architectural technical debt. Architectural technical debt is the often ignored, but ironically one of the most damaging, categories of technical debt.

In this article, I want to dive deeper into one way to manage architectural technical debt (and technical debt as a whole) — architectural observability (AO). AO is a new category of observability that I believe is just as important, if not more so, as application performance management (APM). I believe we need to shift left observability — to the architectural stage — where we can not just see symptoms, but fix core problems.