<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service Reliability on Ivaldo de Oliveira Batista Júnior</title><link>https://ivaldo.eti.br/tags/service-reliability/</link><description>Recent content in Service Reliability on Ivaldo de Oliveira Batista Júnior</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Ivaldo de Oliveira Batista Júnior</copyright><lastBuildDate>Mon, 16 Nov 2026 20:00:00 -0300</lastBuildDate><atom:link href="https://ivaldo.eti.br/tags/service-reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>Your System Is Up, but Your Business Is Stalling: Monitoring Critical Operations Beyond API Uptime</title><link>https://ivaldo.eti.br/blog/api-monitoring-critical-business-operations/</link><pubDate>Mon, 16 Nov 2026 20:00:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/api-monitoring-critical-business-operations/</guid><description>&lt;p&gt;The infrastructure dashboard is green. The servers are responding. The APIs passed every uptime check.&lt;/p&gt;
&lt;p&gt;Yet the sales team cannot complete orders, finance is finding transactions stuck in limbo, and customers are starting to call support.&lt;/p&gt;
&lt;p&gt;From the infrastructure&amp;rsquo;s point of view, everything works. &lt;strong&gt;From the business&amp;rsquo;s point of view, the system is failing.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;There is an important difference between keeping a service available and making sure it actually does what it was built to do. That is the point where observability stops being just an engineering tool and becomes an instrument for managing operational risk.&lt;/p&gt;</description></item><item><title>Does Your Business Depend on External APIs? How to Keep One Failure From Stopping Everything</title><link>https://ivaldo.eti.br/blog/external-api-resilience-business-continuity/</link><pubDate>Mon, 16 Nov 2026 18:30:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/external-api-resilience-business-continuity/</guid><description>&lt;p&gt;At 10 a.m. on a Monday, the shipping-rate provider slows down. It doesn&amp;rsquo;t go down — it just starts responding in 40 seconds instead of 400 milliseconds.&lt;/p&gt;
&lt;p&gt;Within minutes, checkout freezes. Server connections are exhausted waiting for replies. The product catalog, which has nothing to do with shipping, slows down too because it shares the same resources. The support team can no longer look up orders. The dashboard says the site is &amp;ldquo;up,&amp;rdquo; but nobody can buy anything.&lt;/p&gt;</description></item></channel></rss>