高并发的wcf集群

by admin on 2019年7月1日

    

       
相当多场合下基于wcf的复杂性均衡都首荐zookeeper,这样能够具有越来越好的操纵粒度,但zk对C#
比非常小和谐,实现起来相对来讲比较费力,实际处境下,若是

您的负载机制粒度相当的粗劣的话,优先利用nginx就能够解决,不仅可以够落成复杂均衡,又有什么不可兑现双机热备,以细小的代码量完成我们的事情,上面具体享受下。

 

一:打算的资料

 

  1. 话相当的少说,一图胜千言,图中的服务器都以运用vmware设想化,如下图:

     图片 1

《1》 三台windows机器
,四个WCF的windows服务器承载(192.168.23.187,192.168.23.188),一台Client的服务器(192.168.23.1)

《2》 一台Centos机器,用来承载web复杂均衡nginx(192.168.23.190)。

《3》在全部的Client的Hosts文件中加进host映射:【192.168.23.190
cluster.com】,方便通过域名的情势拜访nginx所在服务器的ip地址。

 

二:情状搭建

  1. WCF程序

    既然是测验,明确正是总结的顺序,代码就不完全交给了。

 

《1》
HomeService达成类代码如下(输出当前server的ip地址,方便查看):

 1     public class HomeService : IHomeService
 2     {
 3         public string DoWork(string msg)
 4         {
 5             var ip = Dns.GetHostAddresses(Dns.GetHostName()).FirstOrDefault(i => i.AddressFamily ==
 6                                                                AddressFamily.InterNetwork).ToString();
 7 
 8             return string.Format("当前 request 由 server={0} 返回", ip);
 9         }
10     }

 

《2》 App.Config代码

 1 <?xml version="1.0" encoding="utf-8" ?>
 2 <configuration>
 3   <startup>
 4     <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2" />
 5   </startup>
 6   <system.serviceModel>
 7     <behaviors>
 8       <serviceBehaviors>
 9         <behavior name="">
10           <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
11           <serviceDebug includeExceptionDetailInFaults="false" />
12         </behavior>
13       </serviceBehaviors>
14     </behaviors>
15     <services>
16       <service name="WcfService.HomeService">
17         <endpoint address="/HomeService" binding="basicHttpBinding" contract="WcfService.IHomeService">
18           <identity>
19             <dns value="localhost" />
20           </identity>
21         </endpoint>
22         <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
23         <host>
24           <baseAddresses>
25             <add baseAddress="http://192.168.23.187:8733" />
26           </baseAddresses>
27         </host>
28       </service>
29     </services>
30   </system.serviceModel>
31 </configuration>

 

因为windows的两台机械的ip地址是192.168.23.187,192.168.23.188,所以布署的时候注意一下config中的baseAddress地址。

 

  1. centos上的nginx搭建

   
nginx笔者想大家用的照旧非常多的,去官方网址下载最新的就好【nginx-1.13.6】:http://nginx.org/en/download.html,下载之后,便是常规的三板斧安装!!!

[root@localhost nginx-1.13.6]# ./configure --prefix=/usr/myapp/nginx
[root@localhost nginx-1.13.6]# make && make install

   

    然后在nginx的装置目录下面找到conf文件,修改里面包车型地铁nginx.conf 配置。

[root@localhost nginx]# cd conf
[root@localhost conf]# ls
fastcgi.conf            koi-utf             nginx.conf           uwsgi_params
fastcgi.conf.default    koi-win             nginx.conf.default   uwsgi_params.default
fastcgi_params          mime.types          scgi_params          win-utf
fastcgi_params.default  mime.types.default  scgi_params.default
[root@localhost conf]# vim nginx.conf

 

   
详细安插如下,注意下边“标红”的地点,权重依据1:5的艺术举行调用,关于任何的布局,我们能够在英特网搜一下就可以了。

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    upstream  cluster.com{
                 server 192.168.23.187:8733 weight=1;
                 server 192.168.23.188:8733 weight=5;
                 }

    server {
        listen       80;
        server_name  localhost;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;

        location / {
            root   html;
            index  index.html index.htm;
            proxy_pass http://cluster.com; 
            #设置主机头和客户端真实地址,以便服务器获取客户端真实IP
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header  X-Real-IP  $remote_addr; 
        }

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }

        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
        #
        #location ~ \.php$ {
        #    proxy_pass   http://127.0.0.1;
        #}

        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
        #
        #location ~ \.php$ {
        #    root           html;
        #    fastcgi_pass   127.0.0.1:9000;
        #    fastcgi_index  index.php;
        #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
        #    include        fastcgi_params;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #    deny  all;
        #}
    }


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}


    # HTTPS server
    #
    #server {
    #    listen       443 ssl;
    #    server_name  localhost;

    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_cache    shared:SSL:1m;
    #    ssl_session_timeout  5m;

    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers  on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

 

 3. client端的主次搭建

《1》 第一件事正是将 192.168.23.190
映射到本机的host中去,因为服务不提须要第三方应用,所以加host还是相当的轻便的。

192.168.23.190 cluster.com

图片 2

 

《2》
然后正是client端程序增添服务援用,因为增加了host映射,所以服务援用地址正是”http://cluster.com"。
代码如下:

图片 3

 1     class Program
 2     {
 3         static void Main(string[] args)
 4         {
 5             for (int i = 0; i < 1000; i++)
 6             {
 7                 HomeServiceClient client = new HomeServiceClient();
 8 
 9                 var info = client.DoWork("hello world!");
10 
11                 Console.WriteLine(info);
12 
13                 System.Threading.Thread.Sleep(1000);
14             }
15 
16             Console.Read();
17         }
18     }

 

最后来实行以下顺序,看看1000次巡回中,是还是不是遵从权重1:5
的艺术对后端的wcf举行调用的???

图片 4

图片 5

 

观察未有,是或不是很牛逼,我只需求通过cluster.com举办服务走访,nginx会自动给作者复杂均衡,这就是我们开荒中丰硕轻巧化的wcf复杂均衡。

 

仰望本篇对你有帮带~~~~
  附完整源代码:cluster.zip   
 

 

发表评论

电子邮件地址不会被公开。 必填项已用*标注

网站地图xml地图