<?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>SLO on wid's blog</title><link>https://wid-blog.github.io/en/tags/slo/</link><description>Recent content in SLO on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 15 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/slo/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing and Operating SLAs for Low-Latency Services</title><link>https://wid-blog.github.io/en/posts/tech/architecture/low-latency-sla/</link><pubDate>Mon, 15 Sep 2025 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/architecture/low-latency-sla/</guid><description>An SLA isn&amp;rsquo;t kept by monitoring after the fact — it&amp;rsquo;s built by design and held by operation. Once the SLI for a low-latency service becomes p99 latency rather than availability, timeout budgets, caching, degradation, isolation, and load shedding build the SLA, while p99 SLOs, burn-rate alerting, headroom, deploy gates, and the review cycle hold it.</description></item></channel></rss>