<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Downtime on Scholion</title><link>https://scholion.thluiz.com/tags/downtime/</link><description>Recent content in Downtime on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/downtime/index.xml" rel="self" type="application/rss+xml"/><item><title>Simple Systems Have Less Downtime</title><link>https://scholion.thluiz.com/notes/simple-systems-have-less-downtime/</link><pubDate>Mon, 20 Apr 2020 21:22:45 +0000</pubDate><guid>https://scholion.thluiz.com/notes/simple-systems-have-less-downtime/</guid><description>The article argues that simple systems are easier to operate, troubleshoot, and replace, so they recover faster from failures. It uses ships and startup workflows to show how complexity increases downtime.</description></item><item><title>Zero-downtime Postgres migrations - the hard parts</title><link>https://scholion.thluiz.com/notes/zero-downtime-postgres-migrations-the-hard-parts/</link><pubDate>Fri, 05 Jun 2015 09:35:34 -0300</pubDate><guid>https://scholion.thluiz.com/notes/zero-downtime-postgres-migrations-the-hard-parts/</guid><description>A Postgres migration caused 15 seconds of API downtime because adding a foreign key locked a heavily used referenced table. The post explains why and lists ways to reduce lock-related downtime.</description></item></channel></rss>