Azure-docs: Difference between creating proxy through ServiceProxy and ServiceProxyFactory

[cppcraze]

ServiceProxy.Create<IService>() can already create proxy for different interface, why a factory is provided? How to choose ServiceProxy or ServiceProxyFactory?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 8902374b-b631-9d50-16ef-1899ea2dd29d
• Version Independent ID: 55351e69-aa2a-901c-a563-106b62e3d6ac
• Content: Service remoting by using C# in Service Fabric
• Content Source: articles/service-fabric/service-fabric-reliable-services-communication-remoting.md
• Service: service-fabric
• GitHub Login: @vturecek
• Microsoft Alias: vturecek

[TravisCragg-MSFT]

@cppcraze Thanks for the feedback. We are actively investigating and will get back to you soon.

[mimckitt]

@vturecek @aljo-microsoft could either of you provide some insight into this question?

[aljo-microsoft]

@cppcraze

Could you clarify how the following referenced document content is confusing:

"
Service proxy lifetime
Service proxy creation is a lightweight operation, so you can create as many as you need. Service proxy instances can be reused for as long as they are needed. If a remote procedure call throws an exception, you can still reuse the same proxy instance. Each service proxy contains a communication client used to send messages over the wire. While invoking remote calls, internal checks are performed to determine if the communication client is valid. Based on the results of those checks, the communication client is re-created if needed. Therefore, if an exception occurs, you do not need to re-create ServiceProxy.

Service proxy factory lifetime
ServiceProxyFactory is a factory that creates proxy instances for different remoting interfaces. If you use the API ServiceProxyFactory.CreateServiceProxy to create a proxy, the framework creates a singleton service proxy. It is useful to create one manually when you need to override IServiceRemotingClientFactory properties. Factory creation is an expensive operation. A service proxy factory maintains an internal cache of the communication client. A best practice is to cache the service proxy factory for as long as possible.
"

So explicitly do you need to: "override IServiceRemotingClientFactory properties."?

[mimckitt]

Thanks @aljo-microsoft

@cppcraze any update on this?

[cppcraze]

sorry for not replying yesterday. The documentation is clear on what those two classes can do. I am trying to understand the guideline or design of these two classes, given that they can achieve same purpose that is creating the proxy instance of remoting interface. So when I should use ServiceProxy, when i should use ServiceProxyFactory.

[aljo-microsoft]

@cppcraze
Explicitly if you do not have a known reason to: "override IServiceRemotingClientFactory properties", then you would use ServiceProxy.

@MicahMcKittrick-MSFT

please-close

[cppcraze]

ok, fine, if you guys can't answer the question, just close it.

[mimckitt]

@cppcraze the answer as Alex states is

"Explicitly if you do not have a known reason to: "override IServiceRemotingClientFactory properties", then you would use ServiceProxy."

In addition, as you are a MSFT Employee there are DLs you are reach out to for design assistance if you require it. Feel free to ping me offline and I can provide you with those alias's

[cppcraze]

yeah, thanks Micah. feel free to close.