<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Reliability on Fulgurion Systems Blog</title><link>https://fulgurion.com/blog/tags/reliability/</link><description>Recent content in Reliability on Fulgurion Systems Blog</description><image><title>Fulgurion Systems Blog</title><url>https://fulgurion.com/blog/images/Logo-linkedin.png</url><link>https://fulgurion.com/blog/images/Logo-linkedin.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 00:00:00 -0300</lastBuildDate><atom:link href="https://fulgurion.com/blog/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>Observability Is More Than Logs</title><link>https://fulgurion.com/blog/posts/observability-more-than-logs/</link><pubDate>Fri, 22 May 2026 00:00:00 -0300</pubDate><guid>https://fulgurion.com/blog/posts/observability-more-than-logs/</guid><description>&lt;p&gt;Observability is the ability to understand the internal state of a system by examining its external outputs. It is a broader capability than logging, and the gap between the two becomes obvious the first time a system reaches a state nobody designed for. This is the first post in a series on observability. It covers what the term means, why logs alone leave you debugging in production, the commercial case for investing in observability, and the bar an application has to clear before you can say it has it.&lt;/p&gt;</description></item><item><title>Backend Infrastructure as a Business Concern</title><link>https://fulgurion.com/blog/posts/backend-infrastructure-business-concern/</link><pubDate>Fri, 08 May 2026 00:00:00 -0300</pubDate><guid>https://fulgurion.com/blog/posts/backend-infrastructure-business-concern/</guid><description>&lt;p&gt;A company&amp;rsquo;s ability to operate in its market is bounded by what its backend can absorb: how fast safe changes reach production, whether a regression is contained or systemic, whether one broken component takes the rest down, whether a change has been exercised against production-like state before users see it, and whether the team observes problems before customers do. Each maps to a category of business risk and competitive position.&lt;/p&gt;</description></item></channel></rss>