<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wait-Strategies on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/wait-strategies/</link>
    <description>Recent content in Wait-Strategies on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/wait-strategies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>wait-for-it vs dockerize vs wait4x in 2026: Stop Using sleep 10 in Your Entrypoint</title>
      <link>https://www.pistack.xyz/posts/2026-11-11-container-wait-strategies-wait-for-it-dockerize-wait4x/</link>
      <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-11-container-wait-strategies-wait-for-it-dockerize-wait4x/</guid>
      <description>&lt;p&gt;Your API container booted in 400ms. Your Postgres container took nine seconds to accept connections. The &lt;code&gt;sleep 10&lt;/code&gt; in your entrypoint worked for eleven months — until the day the database had to replay a WAL segment and recovery took 14 seconds. The container crash-looped, the orchestrator marked the service unhealthy, and your deploy failed at 2am for a reason that had nothing to do with the code you shipped.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
