<story><title>Building Microservices the Lean Way, part 2</title><url>http://blog.hubblehq.com/building-microservices-the-lean-way-2/</url><text></text></story><parent_chain><item><author>AndrewHampton</author><text>So here&amp;#x27;s a question we&amp;#x27;ve been talking about at my office. When developing a micro-service on your development machine, do you need to run the whole stack or just the service you&amp;#x27;re working on?&lt;p&gt;For example, let&amp;#x27;s I am working on service A, which depends on services B and C. Do I need to run all 3 apps and their data stores locally?&lt;p&gt;We currently will typically point A to the staging B and C. However, we have some long running jobs that A will initiate on B and B needs to post back to A when it&amp;#x27;s finished. This doesn&amp;#x27;t work when pointing to staging B.</text></item></parent_chain><comment><author>rgarcia</author><text>You should check out a tool we built to solve this problem at Clever: &lt;a href=&quot;https://github.com/clever/aviator&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;clever&amp;#x2F;aviator&lt;/a&gt;&lt;p&gt;It lets us spin up a service + all dependent services locally with a single command.</text></comment>
<story><title>Building Microservices the Lean Way, part 2</title><url>http://blog.hubblehq.com/building-microservices-the-lean-way-2/</url><text></text></story><parent_chain><item><author>AndrewHampton</author><text>So here&amp;#x27;s a question we&amp;#x27;ve been talking about at my office. When developing a micro-service on your development machine, do you need to run the whole stack or just the service you&amp;#x27;re working on?&lt;p&gt;For example, let&amp;#x27;s I am working on service A, which depends on services B and C. Do I need to run all 3 apps and their data stores locally?&lt;p&gt;We currently will typically point A to the staging B and C. However, we have some long running jobs that A will initiate on B and B needs to post back to A when it&amp;#x27;s finished. This doesn&amp;#x27;t work when pointing to staging B.</text></item></parent_chain><comment><author>jasonwocky</author><text>Depends on the use case. For automated testing, if I&amp;#x27;m developing service A, then locally I&amp;#x27;d usually I&amp;#x27;d want to stub B &amp;amp; C with something like Mountebank (&lt;a href=&quot;http://www.mbtest.org/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.mbtest.org&amp;#x2F;&lt;/a&gt;) (though I&amp;#x27;ve never used it to do a post-back as you describe...not sure if it supports that out of the box).&lt;p&gt;If I just wanted to poke around a running system to see how things interact manually, yeah I&amp;#x27;d run everything locally. Probably using Docker images for each dependency service and Vagrant to manage the suite of those images, to preserve my sanity.</text></comment>