Use vagrant to escape tight coupling in SOA
SOA is supposed to decouple development and enable teams to work independently. But many times a developer want to run a development version of a service. Unfortunatlly running a development version of someone else's service requires bootstrapping their environment which becomes more painful as the infrastructure diverges. The real solution is to give consumers of your service the control they need without requiring them to learn your development configuration or become sysadmin specialists in your framework of choice.
Here's a discussion of how you can use virtualization to create that stability and control, and a quick example of how two developers can use vagrant to make it easier for people to develop with and test their code.blog comments powered by Disqus