Q: how do replicas work in tye

Replicas mean there are multiple instances of an application running. In Kubernetes, a ‘Service’ is what is used by an application which will then resolve to one of the instances.

When developing with tye, what will cause the difference instances to be used? Does the GetServiceUri method always resolve to the same instance?

cc @davidfowl @jkotalik

[pattisapu01]

On your localhost, replicas simply creates multiple “instances” of the program. For ex, if you specify “Replicas:2”, you can see 2 instances of the program in task manager on 2 different ports. you need to use an “Ingress” with route filters to load balance when resolving the URL to service replicas with more than 1 instance via “tye” service discovery. https://github.com/dotnet/tye/blob/master/docs/recipes/ingress.md

[tmds]

This is a tcp proxy

@davidfowl what process does the tcp proxying? Is there one such process per service (that has multiple replicas)? Where does this live in the source code?