{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b08be303331246b88fdc053940d03281\" frameborder=\"0\" width=\"1242\" height=\"931\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":931,"width":1242,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":931,"thumbnail_width":1242,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b08be303331246b88fdc053940d03281-29b429ff0f9cb503.gif","duration":190.732,"title":"Optimizing Health Checks in Docker Under Heavy Load 🚀","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."}