Service Directory: Manage all your services in one place at scale

What&#x27;s the relationship between this and a service mesh like Istio? Is Service Directory just for external&#x2F;public clients? Wouldn&#x27;t most of the changes to service endpoints be hidden behind load balancers?<p>They mention Redis and MongoDB as examples of services that could be discovered through Service Directory, but those seem like they would traditionally be used by internal clients.

am I reading this wrong or is this really &quot;just&quot; some sort of &quot;private&quot; DNS zone management for your services?

sounds pretty close to OSB [1][2]<p>So, does this replace or complement (open) service broker?<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;GoogleCloudPlatform&#x2F;gcp-service-broker" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;GoogleCloudPlatform&#x2F;gcp-service-broker</a><p>[2] <a href="https:&#x2F;&#x2F;www.openservicebrokerapi.org" rel="nofollow">https:&#x2F;&#x2F;www.openservicebrokerapi.org</a>

Can someone map this to AWS? Im pretty sure its not related to AWS Directory Service!

“All your X in one place” is snake oil vendor lock-in dressed as convenience.<p>N.B. I have no opinion on Service Directory. It may be a great tool. I just object to the pitch in the headline