So far, we have seen how we can get Vagrant to a stage where our development environment is contained in Vagrant-managed virtual machines, with one of the key aspects being that these virtual machines mimic our production environment. It gives us the flexibility of being able to encapsulate the development environment for different projects so that we can easily switch from one to another without having to modify the software on our own machines.

In many cases, the features we learned so far are enough. However, web projects are becoming more and more complex, with developers continually improving, having to deal with multiple machines in their architecture to help with scalability and stability. While it can be said that scalability and stability issues won't impact our development environment (as we won't have huge amounts of traffic coming to our development environment, unless we load-test it), we want to ensure that the coupling between servers...