<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Engineering - Category - Filipe Felisbino</title><link>https://felisbino.dev/categories/engineering/</link><description>Engineering - Category - Filipe Felisbino</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 15 May 2025 02:16:55 +0000</lastBuildDate><atom:link href="https://felisbino.dev/categories/engineering/" rel="self" type="application/rss+xml"/><item><title>Taming the Beast: Making uWSGI's Harakiri Less Murderous</title><link>https://felisbino.dev/posts/2025-05-15-harakiri-improvement/</link><pubDate>Thu, 15 May 2025 02:16:55 +0000</pubDate><author>Filipe Felisbino</author><guid>https://felisbino.dev/posts/2025-05-15-harakiri-improvement/</guid><description><![CDATA[<p>Back in the ancient times of 2021, when we were still writing all of our code
and doing all troubleshooting without AI assistance, I found myself wrestling
with a particularly angry piece of infrastructure: uWSGI&rsquo;s harakiri mechanism.</p>
<h2 id="the-problem-when-harakiri-goes-too-far">The Problem: When Harakiri Goes Too Far</h2>
<p>Picture this: You&rsquo;re running a Python web app, and suddenly one request decides
to take a leisurely stroll through molasses. Maybe it&rsquo;s waiting on a slow
database query, or perhaps it&rsquo;s gotten lost in an infinite loop of contemplation
about the meaning of life (and JSON parsing).</p>]]></description></item></channel></rss>