<p>I have a service with only one credentials to access another external service using a TCP connection.</p>
<p>Problem: I want to scale the service but i cant have two or more instances using the same credentials, and i dont have more credentials to use it.</p>
<p>So there's a way to scale this service using only one credentials?</p>
<p><a href="https://i.stack.imgur.com/rqAb1.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rqAb1.png" alt="enter image description here" /></a></p>

Gabriel Guedes
<p>Split the bit that communicates with that separate service into another service that stays a singleton.  Make your current service dependent on that other service.  Everything else around your current service can then scale at need.</p>
<p>If your constraint is your I/O with that external service, then scaling your internal service is not going to help.  It's an immovable constraint.  However if the scaling constraint are other parts of your internal service (database, processing, business logic, etc) then this architecture can help.</p>
