Show HN: Mockingjay – Fake servers and consumer-driven contracts

This is a project born of my frustration of making fake servers and CDCs over and over again as we break our monolith into tiny pieces.<p>I figured the requirements for both fake servers and CDCs in a lot of cases are the same. &quot;Given a request, i want this response&quot;. So I thought, why not just define it once in configuration and be done with it. This stops the two things getting out of sync.<p>The wiki has lots of info as to how to use it and what the point of it is. Would appreciate any feedback, apart from mean things.

We use Pact[1], but the idea of flakeyness is interesting. Would you end up with non deterministic builds with the flakeyness? I imagine you could get enough 404&#x27;s to trigger a Circuit Breaker in your application and this would propagate to tests sometimes failing.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;realestate-com-au&#x2F;pact" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;realestate-com-au&#x2F;pact</a>

I&#x27;ve encountered the same frustration and created Dockpit (<a href="https:&#x2F;&#x2F;dockpit.io" rel="nofollow">https:&#x2F;&#x2F;dockpit.io</a>) as a solution; it uses Docker containers though.

A genuine question, how is it differentiated from Stubby? <a href="http:&#x2F;&#x2F;stub.by&#x2F;" rel="nofollow">http:&#x2F;&#x2F;stub.by&#x2F;</a>