Use nginx to build a high-availability, high-concurrency wcf cluster

In many cases, zookeeper is the first choice for complex balancing based on wcf, which can have better control granularity, but zk is not friendly to C#, and it is relatively troublesome to implement. In actual circumstances, if

If the granularity of your load mechanism is very rough, you can use nginx first. It can achieve complex balancing and dual-machine hot backup, and implement our business with the smallest amount of code. I will share it in detail below.

1: Prepared materials

1. Not much to say, a picture is worth a thousand words. The servers in the picture are all virtualized by vmware, as shown below:

《 1》 Three windows machines, two WCF windows servers (192.168.23.187, 192.168.23.188), one Client server (192.168.23.1)

《2》 One Centos machine, used Hosts web complex balancing nginx (192.168.23.190).

《3》Add host mapping in all Client Hosts files: [192.168.23.190 cluster.com] to facilitate access to the IP address of the server where nginx is located through the domain name.

2: Environment setup

1. WCF program

Since it is a test, it must be a simple program, and the code is not completely given.

《1》 HomeService implementation class code is as follows (output the IP address of the current server for easy viewing):

public class HomeService : IHomeService
    {
        public string DoWork(string msg)
        {
            var ip = Dns.GetHostAddresses(Dns.GetHostName()).FirstOrDefault(i => i.AddressFamily ==
                                                        AddressFamily.InterNetwork).ToString();

            return string.Format("当前 request 由 server={0} 返回", ip);
        }

    }

《2》App.Config code

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2" />
 </startup>
  <system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="">

          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />

          <serviceDebug includeExceptionDetailInFaults="false" />
        </behavior>

      </serviceBehaviors>

    </behaviors>

    <services>

      <service name="WcfService.HomeService">

        <endpoint address="/HomeService" binding="basicHttpBinding" contract="WcfService.IHomeService">

          <identity>

            <dns value="localhost" />

          </identity>

        </endpoint>

        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

        <host>

          <baseAddresses>

            <add baseAddress="http://192.168.23.187:8733" />

          </baseAddresses>

        </host>

      </service>

    </services>

  </system.serviceModel>

</configuration>

## Because the ip addresses of the two windows machines are 192.168.23.187, 192.168.23.188 , so pay attention to the baseAddress address in the config when deploying.

2. Setting up nginx on centos

I think everyone uses nginx a lot. Just go to the official website and download the latest one [nginx-1.13.6] : http://nginx.org/en/download.html, after downloading, it is a regular installation of Sanbanaxe! ! !

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

[root@localhost nginx-1.13.6]# make && make install

Then find the conf file under the nginx installation directory and modify the nginx.conf configuration inside.

[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.defaultfastcgi_params mime.types scgi_params win-utf
fastcgi_params.default mime.types.default scgi_params.default[root@localhost conf]# vim nginx.conf

The detailed configuration is as follows. Pay attention to the "red" area below. The weight is called according to the method of 1:5. For other configurations, you can search online. .

#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-side program construction

《1》The first thing is to map 192.168.23.190 to the local machine Go to the host, because the service is not provided to third parties, so it is very easy to add the host.

192.168.23.190 cluster.com

"2" Then the client program adds a service reference, the code is as follows ：

class Program

  {
       static void Main(string[] args)
      {
           for (int i = 0; i < 1000; i++)
          {
               HomeServiceClient client = new HomeServiceClient();

               var info = client.DoWork("hello world!");


             Console.WriteLine(info);


              System.Threading.Thread.Sleep(1000);14            }



         Console.Read();

      }

}

Finally, execute the following program to see if the back-end wcf is processed with a weight of 1:5 in 1000 cycles. Called? ? ?

See, isn’t it awesome? I only need to access the service through cluster.com , nginx will automatically give me complex equalization, which is the very simplified wcf complex equalization in our development.

The above is the detailed content of Use nginx to build a high-availability, high-concurrency wcf cluster. For more information, please follow other related articles on the PHP Chinese website!