<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b08be303331246b88fdc053940d03281&quot; frameborder=&quot;0&quot; width=&quot;1242&quot; height=&quot;931&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>931</height><width>1242</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>931</thumbnail_height><thumbnail_width>1242</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b08be303331246b88fdc053940d03281-29b429ff0f9cb503.gif</thumbnail_url><duration>190.732</duration><title>Optimizing Health Checks in Docker Under Heavy Load 🚀</title><description>In this video, I demonstrate how a separate health check app works in a Docker environment, particularly under heavy load conditions. I highlight the importance of using a dedicated health check on port 4001, as the main app on port 4000 may hang during high traffic, risking the termination of the pod. I simulate a high load using a locust test, which shows that while the main app may fail, the health app remains operational. I encourage you to consider implementing a separate health check application to ensure system reliability. Please let me know if you have any questions or need further clarification on this setup.</description></oembed>