<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Application Orchestration on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/application-orchestration/</link><description>Recent content in Application Orchestration on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/application-orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 7: Docker Compose - Orchestrating Multi-Container Applications</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/docker-compose-multi-container/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/docker-compose-multi-container/</guid><description>&lt;h2 id="introduction-to-orchestrating-multi-container-applications"&gt;Introduction to Orchestrating Multi-Container Applications&lt;/h2&gt;
&lt;p&gt;Welcome back, future DevOps maestro! In our last chapter, we mastered the art of running single Docker containers and even crafted our own custom images using &lt;code&gt;Dockerfile&lt;/code&gt;. That was a fantastic start, but in the real world, applications are rarely just one isolated container. Think about a typical web application: you&amp;rsquo;ll likely have a web server, a backend API, a database, maybe a cache, and more – all needing to talk to each other.&lt;/p&gt;</description></item></channel></rss>