Well, linkerd was what the article was about, so it&#x27;s what I was referring to.  A &quot;sidecar&quot; sounds like the more established term for what I was calling an ambassador proxy, so it&#x27;s nice to learn that that&#x27;s what people call this pattern.<p>Your explanation sounds a bit &quot;no duh&quot; though, since I can&#x27;t imagine any way of implementing this pattern that <i>doesn&#x27;t</i> abstract away knowledge of how to reach remote partners, perform health checks, load balancing, retry logic, etc.  It&#x27;s generally what the term &quot;proxy&quot; implies.  Or am I missing something?<p>Edit: I think my confusion is caused by my experience with running vanilla Mesos (not Marathon or DCOS, but our own custom frameworks), where it&#x27;s expected that you just have to implement this stuff yourself.  I never even thought of open sourcing or productizing what I&#x27;ve written, because I kind of thought that everybody else must be rolling their own quick solutions for these problems too?  I admit I&#x27;m probably the one with a messed up worldview though.<p>I think the mesos community is still in the phase of picking the winners for best practices, and hopefully one day it&#x27;ll be obvious that you use services like linkerd and don&#x27;t roll your own solution.