As you make more use of Docker, your solution will become distributed across more containers—either running custom code that you split out from a monolith or tried and trusted third-party software from Docker Hub or a third-party registry.
NerdDinner now runs across five containers—SQL Server, the original web app, the new homepage, the NATS message queue, and the message handler. There are dependencies between the containers, and they need to be started in the correct order and created with the correct names so that components can be found using Docker's service discovery.
In the next chapter, I'll use Docker Compose to declaratively map out these dependencies. For now, I have a PowerShell script called ch05-run-nerd-dinner_part-1.ps1 that explicitly starts the containers with the correct configuration:
docker container...
