WCF正确的架构解决方案 [英] WCF proper architectial solution

问题描述

您好，



我的WCF服务存在架构问题。

当前服务每天可以解决1000个请求。这是单线程服务（多线程是不可能的，因为第三部分dll）

我有5颗卫星和排队引擎。

每日容量约为5k请求。客户需求大约是12k请求...



我想知道你是否知道比将服务复制到3个不同位置更好的解决方案，将它们重命名为service1，service2，service3并使用不同的URL运行所有这些（服务的实例）每个卫星？

Hello,

I have a architectural problem with WCF Services.
Current service is able to resolve 1000 request per a day. It's single thread service (multithreading is not possible, because of third part dlls)
I have 5 satellites and queuing engine.
Daily capacity is around 5k request. Client needs are around 12k requests...

I am wondering if you know any better solution than copying service to 3 different locations, rename them to service1, service2, service3 and run all of them (instances of the service) per satellite with different URL?

推荐答案

如果您的DLL是第三方DLL并且受某些使用限制（试用/免费）那么我不认为通过创建新服务会帮助你。实际上，您需要在具有相同服务名称的单独服务器上实现它们，并且需要实现负载平衡。



但请记住，如果是这样，则硬件成本将高于第三方解决方案:)



谢谢

Rushi

If your DLL is third party DLL and under some usage restriction (trial/free version) then I don't think by creating new Service will help you here. You actually need to implement them on separate servers with same service name and need to implement Load Balancing.

But keep in mind that if that is the case then Hardware cost will be higher then thirdparty solutions :)

Thanks
Rushi

这篇关于WCF正确的架构解决方案的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！