首页 文章 精选 留言 我的

.NET Core微服务之路：基于Consul最少集群实现服务的注册与发现（一）

2018-10-13 644

Consul介绍

　　 Consul是HashiCorp公司推出的开源工具[开源地址：https://github.com/hashicorp/consul]，用于实现分布式系统的服务发现与配置。
 
　　 与市面上其他系统比较如下：
 
　　 总体而言， Consul用Golang实现，因此具有天然可移植性（支持Linux、windows和Mac OS X）；安装包仅包含一个可执行文件，方便部署，与Docker等轻量级容器可 无缝配合。
此外，关于Consul的架构以及相关的角色，如下图所示：
　　 以Server模式运行的Consul Agent节点用于维护Consul集群的状态，官方建议每个Consul Cluster至少有 3个或以上的运行在Server Mode的Agent，Client节点不限。Consul支持多数据中心，每个数据中心的Consul Cluster都会在运行于Server模式下的Agent节点中选出一个Leader节点，这个选举过程通过Consul实现的raft协议保证，多个 Server节点上的Consul数据信息是强一致的。处于Client Mode的Consul Agent节点比较简单，无状态，仅仅负责将请求转发给Server Agent节点。
 

集群搭建

　　笔者打算通过五台Centos7来搭建Consul集群，借助VMware Workstation搭建，当然，最主要的是这台虚拟主机一定要相互ping通，最好关闭防火墙，而且，虚拟机也需要和宿主机（实比如笔者的Windows10操作系统）ping通，具体问题和配置可搜索一下，图片如下：

 

　　其中130作为leader角色，129和131作为follower角色，当然，在实际环境中，leader的角色不一定是固定的，会随着环境变化而变化（比如网络断了、宕机了等等）这个我们后续来验证。132和133作为客户端，并安装NET Core 2.1环境，再次提示，一定要保证在这个环境中的所有系统相互之间均能Ping通。

 

step1：关闭防火墙

systemctl stop firewalld
systemctl disable firewalld

 

step2：安装consul

wget https://releases.hashicorp.com/consul/1.3.0/consul_1.3.0_linux_amd64.zip
unzip consul_1.3.0_linux_amd64.zip

 

step3：节点1

./consul agent -server -ui -bootstrap-expect=3 -data-dir=/tmp/consul -node=consul-1 -client=0.0.0.0 -bind=192.168.153.129 -datacenter=dc1 #设置129为服务器
bootstrap_expect > 0: expecting 3 servers
==> Starting Consul agent...
==> Consul agent running!
           Version: 'v1.3.0'
           Node ID: 'c612a043-8906-d6e1-8f4b-ef1c8afb371b'
         Node name: 'consul-1'
        Datacenter: 'dc1' (Segment: '<all>')
            Server: true (Bootstrap: false)
       Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
      Cluster Addr: 192.168.153.129 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2018/10/15 04:53:30 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb3777 Address:192.168.153.131:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371a Address:192.168.153.130:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371b Address:192.168.153.129:8300}]
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-1.dc1 192.168.153.129
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-1 192.168.153.129
    2018/10/15 04:53:30 [WARN] agent: Service name "LZZ.DEV.ClientService" will not be discoverable via DNS due to invalid characters. Valid characters include all alpha-numerics and dashes.
    2018/10/15 04:53:30 [WARN] agent: Service name "LZZ.PRO.ClientService" will not be discoverable via DNS due to invalid characters. Valid characters include all alpha-numerics and dashes.
    2018/10/15 04:53:30 [WARN] agent: check 'service:17947fbe-24ee-40e1-8e49-ea42415ada23' has deregister interval below minimum of 1m0s
    2018/10/15 04:53:30 [WARN] agent: check 'service:81d5b247-73d1-4ae5-9d1a-208770ca4e6a' has deregister interval below minimum of 1m0s
    2018/10/15 04:53:30 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp)
    2018/10/15 04:53:30 [INFO] raft: Node at 192.168.153.129:8300 [Follower] entering Follower state (Leader: "")
    2018/10/15 04:53:30 [INFO] serf: Attempting re-join to previously known node: consul-3.dc1: 192.168.153.131:8302
    2018/10/15 04:53:30 [INFO] serf: Attempting re-join to previously known node: LZZ.PRODUCTS.WebServer: 192.168.153.133:8301
    2018/10/15 04:53:30 [INFO] consul: Adding LAN server consul-1 (Addr: tcp/192.168.153.129:8300) (DC: dc1)
    2018/10/15 04:53:30 [INFO] consul: Raft data found, disabling bootstrap mode
    2018/10/15 04:53:30 [INFO] consul: Handled member-join event for server "consul-1.dc1" in area "wan"
    2018/10/15 04:53:30 [WARN] agent/proxy: running as root, will not start managed proxies
    2018/10/15 04:53:30 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp)
    2018/10/15 04:53:30 [INFO] agent: Started HTTP server on [::]:8500 (tcp)
    2018/10/15 04:53:30 [INFO] agent: started state syncer
    2018/10/15 04:53:30 [INFO] serf: Attempting re-join to previously known node: consul-3: 192.168.153.131:8301
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-3.dc1 192.168.153.131
    2018/10/15 04:53:30 [WARN] memberlist: Refuting an alive message
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-2.dc1 192.168.153.130
    2018/10/15 04:53:30 [INFO] serf: Re-joined to previously known node: consul-3.dc1: 192.168.153.131:8302
    2018/10/15 04:53:30 [INFO] consul: Handled member-join event for server "consul-3.dc1" in area "wan"
    2018/10/15 04:53:30 [INFO] consul: Handled member-join event for server "consul-2.dc1" in area "wan"
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-3 192.168.153.131
    2018/10/15 04:53:30 [WARN] memberlist: Refuting a suspect message (from: consul-1)
    2018/10/15 04:53:30 [INFO] serf: EventMemberJoin: consul-2 192.168.153.130
    2018/10/15 04:53:30 [INFO] serf: Re-joined to previously known node: consul-3: 192.168.153.131:8301
    2018/10/15 04:53:30 [INFO] consul: Adding LAN server consul-3 (Addr: tcp/192.168.153.131:8300) (DC: dc1)
    2018/10/15 04:53:30 [INFO] consul: Adding LAN server consul-2 (Addr: tcp/192.168.153.130:8300) (DC: dc1)

 

　　Client Addr的地址是[0.0.0.0]，代表本机上的所有IPv4地址。集群地址是：192.168.153.129。稍后我们介绍命令一些主要参数的的作用。
 

step4：节点2

./consul agent -server -ui -bootstrap-expect=3 -data-dir=/tmp/consul -node=consul-2 -client=0.0.0.0 -bind=192.168.153.130 -datacenter=dc1 -join 192.168.153.129 # join 加入到129中
bootstrap_expect > 0: expecting 3 servers
==> Starting Consul agent...
==> Joining cluster...
    Join completed. Synced with 1 initial agents
==> Consul agent running!
           Version: 'v1.3.0'
           Node ID: 'c612a043-8906-d6e1-8f4b-ef1c8afb371a'
         Node name: 'consul-2'
        Datacenter: 'dc1' (Segment: '<all>')
            Server: true (Bootstrap: false)
       Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
      Cluster Addr: 192.168.153.130 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2018/10/15 04:56:36 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb3777 Address:192.168.153.131:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371a Address:192.168.153.130:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371b Address:192.168.153.129:8300}]
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-2.dc1 192.168.153.130
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-2 192.168.153.130
    2018/10/15 04:56:36 [INFO] raft: Node at 192.168.153.130:8300 [Follower] entering Follower state (Leader: "")
    2018/10/15 04:56:36 [INFO] serf: Attempting re-join to previously known node: consul-3.dc1: 192.168.153.131:8302
    2018/10/15 04:56:36 [INFO] serf: Attempting re-join to previously known node: consul-3: 192.168.153.131:8301
    2018/10/15 04:56:36 [INFO] consul: Adding LAN server consul-2 (Addr: tcp/192.168.153.130:8300) (DC: dc1)
    2018/10/15 04:56:36 [INFO] consul: Raft data found, disabling bootstrap mode
    2018/10/15 04:56:36 [INFO] consul: Handled member-join event for server "consul-2.dc1" in area "wan"
    2018/10/15 04:56:36 [WARN] memberlist: Refuting a suspect message (from: consul-2)
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-1 192.168.153.129
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-3 192.168.153.131
    2018/10/15 04:56:36 [INFO] serf: Re-joined to previously known node: consul-3: 192.168.153.131:8301
    2018/10/15 04:56:36 [INFO] consul: Adding LAN server consul-1 (Addr: tcp/192.168.153.129:8300) (DC: dc1)
    2018/10/15 04:56:36 [INFO] consul: Adding LAN server consul-3 (Addr: tcp/192.168.153.131:8300) (DC: dc1)
    2018/10/15 04:56:36 [WARN] memberlist: Refuting a suspect message (from: consul-2.dc1)
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-1.dc1 192.168.153.129
    2018/10/15 04:56:36 [INFO] serf: EventMemberJoin: consul-3.dc1 192.168.153.131
    2018/10/15 04:56:36 [INFO] serf: Re-joined to previously known node: consul-3.dc1: 192.168.153.131:8302
    2018/10/15 04:56:36 [INFO] consul: Handled member-join event for server "consul-1.dc1" in area "wan"
    2018/10/15 04:56:36 [INFO] consul: Handled member-join event for server "consul-3.dc1" in area "wan"
    2018/10/15 04:56:36 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp)
    2018/10/15 04:56:36 [WARN] agent/proxy: running as root, will not start managed proxies
    2018/10/15 04:56:36 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp)
    2018/10/15 04:56:36 [INFO] agent: Started HTTP server on [::]:8500 (tcp)
    2018/10/15 04:56:36 [INFO] agent: (LAN) joining: [192.168.153.129]
    2018/10/15 04:56:36 [INFO] agent: (LAN) joined: 1 Err: <nil>
    2018/10/15 04:56:36 [INFO] agent: started state syncer
 

step5：节点3

./consul agent -server -ui -bootstrap-expect=3 -data-dir=/tmp/consul -node=consul-3 -client=0.0.0.0 -bind=192.168.153.131 -datacenter=dc1 -join 192.168.153.129
bootstrap_expect > 0: expecting 3 servers
==> Starting Consul agent...
==> Joining cluster...
    Join completed. Synced with 1 initial agents
==> Consul agent running!
           Version: 'v1.3.0'
           Node ID: 'c612a043-8906-d6e1-8f4b-ef1c8afb3777'
         Node name: 'consul-3'
        Datacenter: 'dc1' (Segment: '<all>')
            Server: true (Bootstrap: false)
       Client Addr: [0.0.0.0] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
      Cluster Addr: 192.168.153.131 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2018/10/15 05:01:15 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb3777 Address:192.168.153.131:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371b Address:192.168.153.129:8300} {Suffrage:Voter ID:c612a043-8906-d6e1-8f4b-ef1c8afb371a Address:192.168.153.130:8300}]
    2018/10/15 05:01:15 [INFO] raft: Node at 192.168.153.131:8300 [Follower] entering Follower state (Leader: "")
    2018/10/15 05:01:15 [INFO] serf: EventMemberJoin: consul-3.dc1 192.168.153.131
    2018/10/15 05:01:15 [INFO] serf: EventMemberJoin: consul-3 192.168.153.131
    2018/10/15 05:01:15 [INFO] serf: Attempting re-join to previously known node: consul-1.dc1: 192.168.153.129:8302
    2018/10/15 05:01:15 [INFO] serf: Attempting re-join to previously known node: consul-1: 192.168.153.129:8301
    2018/10/15 05:01:15 [INFO] consul: Adding LAN server consul-3 (Addr: tcp/192.168.153.131:8300) (DC: dc1)
    2018/10/15 05:01:15 [INFO] consul: Raft data found, disabling bootstrap mode
    2018/10/15 05:01:15 [INFO] consul: Handled member-join event for server "consul-3.dc1" in area "wan"
    2018/10/15 05:01:15 [WARN] agent/proxy: running as root, will not start managed proxies
    2018/10/15 05:01:15 [INFO] agent: Started DNS server 0.0.0.0:8600 (udp)
    2018/10/15 05:01:15 [INFO] agent: Started DNS server 0.0.0.0:8600 (tcp)
    2018/10/15 05:01:15 [INFO] agent: Started HTTP server on [::]:8500 (tcp)
    2018/10/15 05:01:15 [INFO] agent: (LAN) joining: [192.168.153.129]
    2018/10/15 05:01:15 [INFO] serf: EventMemberJoin: consul-1 192.168.153.129
    2018/10/15 05:01:15 [INFO] serf: Re-joined to previously known node: consul-1: 192.168.153.129:8301
    2018/10/15 05:01:15 [INFO] consul: Adding LAN server consul-1 (Addr: tcp/192.168.153.129:8300) (DC: dc1)
    2018/10/15 05:01:15 [INFO] serf: EventMemberJoin: consul-1.dc1 192.168.153.129
    2018/10/15 05:01:15 [INFO] serf: Re-joined to previously known node: consul-1.dc1: 192.168.153.129:8302
    2018/10/15 05:01:15 [INFO] consul: Handled member-join event for server "consul-1.dc1" in area "wan"
    2018/10/15 05:01:15 [INFO] agent: (LAN) joined: 1 Err: <nil>
    2018/10/15 05:01:15 [INFO] agent: started state syncer
 

step6：客户端1

./consul agent -bind 192.168.153.132 -client 192.168.153.132 -data-dir=/tmp/consul -node LZZ.DEV.WebServer -join 192.168.153.129
==> Starting Consul agent...
==> Joining cluster...
    Join completed. Synced with 1 initial agents
==> Consul agent running!
           Version: 'v1.3.0'
           Node ID: 'c7125043-8906-d6e1-8f4b-ef1c8afb371b'
         Node name: 'LZZ.DEV.WebServer'
        Datacenter: 'dc1' (Segment: '')
            Server: false (Bootstrap: false)
       Client Addr: [192.168.153.132] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
      Cluster Addr: 192.168.153.132 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2018/10/15 05:03:15 [WARN] agent: Node name "LZZ.DEV.WebServer" will not be discoverable via DNS due to invalid characters. Valid characters include all alpha-numerics and dashes.
    2018/10/15 05:03:15 [INFO] serf: EventMemberJoin: LZZ.DEV.WebServer 192.168.153.132
    2018/10/15 05:03:15 [INFO] agent: Started DNS server 192.168.153.132:8600 (udp)
    2018/10/15 05:03:15 [WARN] agent/proxy: running as root, will not start managed proxies
    2018/10/15 05:03:15 [INFO] agent: Started DNS server 192.168.153.132:8600 (tcp)
    2018/10/15 05:03:15 [INFO] agent: Started HTTP server on 192.168.153.132:8500 (tcp)
    2018/10/15 05:03:15 [INFO] agent: (LAN) joining: [192.168.153.129]
    2018/10/15 05:03:15 [INFO] serf: EventMemberJoin: consul-1 192.168.153.129
    2018/10/15 05:03:15 [INFO] serf: EventMemberJoin: consul-3 192.168.153.131
    2018/10/15 05:03:15 [INFO] agent: (LAN) joined: 1 Err: <nil>
    2018/10/15 05:03:15 [INFO] agent: started state syncer
    2018/10/15 05:03:15 [INFO] consul: adding server consul-1 (Addr: tcp/192.168.153.129:8300) (DC: dc1)
    2018/10/15 05:03:15 [INFO] consul: adding server consul-3 (Addr: tcp/192.168.153.131:8300) (DC: dc1)
    2018/10/15 05:03:15 [INFO] agent: Synced node info

 

step6：客户端2

./consul agent -bind 192.168.153.133 -client 192.168.153.133 -data-dir=/tmp/consul -node LZZ.PRO.WebServer -join 192.168.153.129
==> Starting Consul agent...
==> Joining cluster...
    Join completed. Synced with 1 initial agents
==> Consul agent running!
           Version: 'v1.3.0'
           Node ID: '1aa2a043-8906-d6e1-8f4b-ef1c8afb371b'
         Node name: 'LZZ.PRO.WebServer'
        Datacenter: 'dc1' (Segment: '')
            Server: false (Bootstrap: false)
       Client Addr: [192.168.153.133] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
      Cluster Addr: 192.168.153.133 (LAN: 8301, WAN: 8302)
           Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false

==> Log data will now stream in as it occurs:

    2018/10/15 05:04:26 [WARN] agent: Node name "LZZ.PRO.WebServer" will not be discoverable via DNS due to invalid characters. Valid characters include all alpha-numerics and dashes.
    2018/10/15 05:04:26 [INFO] serf: EventMemberJoin: LZZ.PRO.WebServer 192.168.153.133
    2018/10/15 05:04:26 [INFO] agent: Started DNS server 192.168.153.133:8600 (udp)
    2018/10/15 05:04:26 [WARN] agent/proxy: running as root, will not start managed proxies
    2018/10/15 05:04:26 [INFO] agent: Started DNS server 192.168.153.133:8600 (tcp)
    2018/10/15 05:04:26 [INFO] agent: Started HTTP server on 192.168.153.133:8500 (tcp)
    2018/10/15 05:04:26 [INFO] agent: (LAN) joining: [192.168.153.129]
    2018/10/15 05:04:26 [INFO] serf: EventMemberJoin: LZZ.DEV.WebServer 192.168.153.132
    2018/10/15 05:04:26 [INFO] serf: EventMemberJoin: consul-3 192.168.153.131
    2018/10/15 05:04:26 [INFO] serf: EventMemberJoin: consul-1 192.168.153.129
    2018/10/15 05:04:26 [INFO] agent: (LAN) joined: 1 Err: <nil>
    2018/10/15 05:04:26 [INFO] agent: started state syncer
    2018/10/15 05:04:26 [INFO] consul: adding server consul-3 (Addr: tcp/192.168.153.131:8300) (DC: dc1)
    2018/10/15 05:04:26 [INFO] consul: adding server consul-1 (Addr: tcp/192.168.153.129:8300) (DC: dc1)
    2018/10/15 05:04:26 [INFO] agent: Synced node info

  

  • -node：节点的名称
  • -bind：绑定的一个地址，用于节点之间通信的地址，可以是内外网，必须是可以访问到的地址
  • -server：这个就是表示这个节点是个server
  • -client：这个表示这个节点是个client
  • -bootstrap-expect：这个就是表示期望提供的SERVER节点数目，数目一达到，它就会被激活，然后就是LEADER了
　　 这样，五台服务器上的consul均已配置和启动完成，接下来我们看看他们之间的关系
 

step7：查看所有consul成员

./consul members
Node               Address               Status  Type    Build  Protocol  DC   Segment
consul-1           192.168.153.129:8301  alive   server  1.3.0  2         dc1  <all>
consul-2           192.168.153.130:8301  failed  server  1.3.0  2         dc1  <all>
consul-3           192.168.153.131:8301  alive   server  1.3.0  2         dc1  <all>
LZZ.DEV.WebServer  192.168.153.132:8301  alive   client  1.3.0  2         dc1  <default>
LZZ.PRO.WebServer  192.168.153.133:8301  alive   client  1.3.0  2         dc1  <default>
 　　如上可知，129，130，131三台consul的类型均是server类型，而132和133为client类型，极小化的集群搭建成功
 

step8：查看服务成员类型
 

./consul operator raft list-peers
Node      ID                                    Address               State     Voter  RaftProtocol
consul-3  c612a043-8906-d6e1-8f4b-ef1c8afb3777  192.168.153.131:8300  follower  true   3
consul-2  c612a043-8906-d6e1-8f4b-ef1c8afb371a  192.168.153.130:8300  follower  true   3
consul-1  c612a043-8906-d6e1-8f4b-ef1c8afb371b  192.168.153.129:8300  leader    true   3

 　　由图中可知，129目前为leader类型，为了验证之前“leader随环境变化而变化”的论证，我特意输入了命令“reboot”，请接着继续看下去。

 

step9：关闭一台服务，测试leader状态

　　当129机器重新连上Consul后，我们再输入consul operator raft list-peers，可以看到此时的leader已经变为131的机器上面。
  
Node       ID                                    Address               State     Voter  RaftProtocol
consul-3   c612a043-8906-d6e1-8f4b-ef1c8afb3777  192.168.153.131:8300  leader    true   3
consul-1   c612a043-8906-d6e1-8f4b-ef1c8afb371b  192.168.153.129:8300  follower  true   3
consul-2   c612a043-8906-d6e1-8f4b-ef1c8afb371a  192.168.153.130:8300  follower  true   3
　　所以，leader会随着环境的变化而变化，并且但只要超过一半的Server（这里是2/3还活着）还活着，集群是可以正常工作的。这也是为什么像Consul、ZooKeeper这样的分布式管理组件推荐我们使用3个或5个节点以上来部署的原因。
 

step10：通过WEB查看服务状态

　　我们还可以通过http://192.168.153.129:8500来查看整个集群的状态。

 

　　接下来，我们创建一个net core的webApi应用程序，来向consul注册一个服务。
 

创建ASP.NET Core程序

　　创建一个ASP.NET Web Application应用程序，项目名称自定

 
 
　　创建一个 HealthController控制器，用于提示该服务的状态。 
using Microsoft.AspNetCore.Mvc;

namespace LZZ.DEV.WebServer.Controllers
{
    [Produces("application/json")]
    [Route("api/Health")]
    public class HealthController : Controller
    {
        [HttpGet]
        public IActionResult Get() => Ok("ok");
    }
}

 

 　　再创建一个应用程序扩展来建立连接和注册服务，利用Net core的管道灵活特性，我们可以非常容易的建立自己的扩展

using System;
using Consul;
using LZZ.DEV.WebServer.Models;
using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.Hosting;

namespace LZZ.DEV.WebServer
{
    public static class AppBuilderExtensions
    {
        public static IApplicationBuilder RegisterConsul(this IApplicationBuilder app,
            IApplicationLifetime lifetime,
            ServiceEntity serviceEntity)
        {
            var consulClient = new ConsulClient(x =>
                x.Address = new Uri($"http://{serviceEntity.ConsulIP}:{serviceEntity.ConsulPort}")); //请求注册的 Consul 地址
            var httpCheck = new AgentServiceCheck()
            {
                DeregisterCriticalServiceAfter = TimeSpan.FromSeconds(5), // 服务启动多久后注册
                Interval = TimeSpan.FromSeconds(10), // 健康检查时间间隔，或者称为心跳间隔
                HTTP = $"http://{serviceEntity.IP}:{serviceEntity.Port}/api/health", // 健康检查地址
                Timeout = TimeSpan.FromSeconds(5)    // 超时时间
            };

            // Register service with consul
            var registration = new AgentServiceRegistration()
            {
                Checks = new[] {httpCheck},
                ID = Guid.NewGuid().ToString(),
                Name = serviceEntity.ServiceName,
                Address = serviceEntity.IP,
                Port = serviceEntity.Port,
                Tags =
                    new[] {$"urlprefix-/{serviceEntity.ServiceName}"} // 添加 urlprefix-/servicename 格式的 tag 标签，以便 Fabio 识别
            };

            consulClient.Agent.ServiceRegister(registration).Wait(); // 服务启动时注册，内部实现其实就是使用 Consul API 进行注册（HttpClient发起）
            lifetime.ApplicationStopping.Register(() =>
            {
                consulClient.Agent.ServiceDeregister(registration.ID).Wait(); // 服务停止时取消注册
            });

            return app;
        }
    }
}

 

　　当然，我们要使用consual，还需要安装consul依赖包
 
 
 　　最后，我们在Startup.cs的Configure配置函数中，增加启动时注册本地条目到consual，完整代码如下 
 1         public void Configure(IApplicationBuilder app, IHostingEnvironment env, IApplicationLifetime lifetime)
 2         {
 3             app.UseMvc(routes =>
 4             {
 5                 routes.MapRoute(
 6                     name: "default",
 7                     template: "{controller=Home}/{action=Index}/{id?}");
 8             });
 9 
10             var serviceEntity = new ServiceEntity
11             {
12                 IP = "192.168.0.196",
13                 Port = Convert.ToInt32(Configuration["Service:Port"]),
14                 ServiceName = Configuration["Service:Name"],
15                 ConsulIP = Configuration["Consul:IP"],
16                 ConsulPort = Convert.ToInt32(Configuration["Consul:Port"])
17             };
18             app.RegisterConsul(lifetime, serviceEntity);
19         }
　　
　　appsettings.json配置文件如下： 
 1 {
 2   "Service": {
 3     "Name": "LZZ.DEV.ClientService",
 4     "Port": "5000"
 5   },
 6   "Consul": {
 7     "IP": "192.168.0.115",
 8     "Port": "8500"
 9   },
10   "Logging": {
11     "LogLevel": {
12       "Default": "Warning"
13     }
14   },
15   "AllowedHosts": "*"
16 }
　　
　　好了，我们按下Ctrl+F5启动这个web应用程序瞧瞧。一切顺利，LZZ.DEV.WebServer已经被成功注册到consul中，使用相同方法也注册LZZ.PRO.WebServer到Consul中。
 

 

 

　　我们还可以通过http://192.168.153.129:8500/v1/catalog/service/LZZ.PRO.ClientService来访问consul注册这条服务的详细信息。
  
[
  {
    "ID": "c612a043-8906-d6e1-8f4b-ef1c8afb371b",
    "Node": "consul-1",
    "Address": "192.168.153.129",
    "Datacenter": "dc1",
    "TaggedAddresses": {
      "lan": "192.168.153.129",
      "wan": "192.168.153.129"
    },
    "NodeMeta": {
      "consul-network-segment": ""
    },
    "ServiceKind": "",
    "ServiceID": "81d5b247-73d1-4ae5-9d1a-208770ca4e6a",
    "ServiceName": "LZZ.PRO.ClientService",
    "ServiceTags": [
      "urlprefix-/LZZ.PRO.ClientService"
    ],
    "ServiceAddress": "192.168.153.132",
    "ServiceWeights": {
      "Passing": 1,
      "Warning": 1
    },
    "ServiceMeta": {
      
    },
    "ServicePort": 5000,
    "ServiceEnableTagOverride": false,
    "ServiceProxyDestination": "",
    "ServiceProxy": {
      
    },
    "ServiceConnect": {
      
    },
    "CreateIndex": 2632,
    "ModifyIndex": 2632
  }
]

　　关注ServiceAddress和ServicePort，即可完成对服务的调用。

 

总结

　　本篇主要介绍以最少化的集群创建了一个consul集群，具体各项细节都没深入研究，后续有时间我会慢慢深入，毕竟ASP.NET core天生就是一个做微服务的，感谢博客园的各位大神资料和参考。

 

参考

　　田园里的蟋蟀：《Docker & Consul & Fabio & ASP.NET Core 2.0 微服务跨平台实践》

 

感谢阅读！！

上一篇 下一篇
优秀的个人博客,低调大师

微信关注我们

原文链接：https://yq.aliyun.com/articles/665174

转载内容版权归作者及来源网站所有！

低调大师中文资讯倾力打造互联网数据资讯、行业资源、电子商务、移动互联网、网络营销平台。持续更新报道IT业界、互联网、市场资讯、驱动更新,是最及时权威的产业资讯及硬件资讯报道平台。

阿里P8架构师谈：高并发架构解决方案总结

一、关于高并发 高并发是指在同一个时间点，有很多用户同时访问URL地址，比如：淘宝的双11、双12，就会产生高并发。又如贴吧的爆吧，就是恶意的高并发请求，也就是DDOS攻击。 1 高并发会来带的后果 服务端：导致站点服务器/DB服务器资源被占满崩溃，数据的存储和更新结果和理想的设计是不一样的，比如：出现重复的数据记录，多次添加了用户积分等。 用户角度：网站打不开 服务器雪崩： 2 并发下的数据处理 通过表设计，如：记录表添加唯一约束，数据处理逻辑使用事物防止并发下的数据错乱问题。通过服务端锁进程防止包并发下的数据错乱问题。 这里主要讲述的是在并发请求下的数据逻辑处理的接口，如何保证数据的一致性和完整性，这里的并发可能是大量用户发起的，也可能攻击者通过并发工具发起的并发请求。 例子1：通过表设计防止并发导致数据错乱 需求点： 【签到功能】一天一个用户只能
2018-10-14
764
上一篇

Spring-涉及到的设计模式汇总

1. 简单工厂 又叫做静态工厂方法（StaticFactory Method）模式，但不属于23种GOF设计模式之一。 简单工厂模式的实质是由一个工厂类根据传入的参数，动态决定应该创建哪一个产品类。 Spring中的BeanFactory就是简单工厂模式的体现，根据传入一个唯一的标识来获得Bean对象，但是否是在传入参数后创建还是传入参数前创建这个要根据具体情况来定。 2. 工厂方法（Factory Method） 定义一个用于创建对象的接口，让子类决定实例化哪一个类。Factory Method使一个类的实例化延迟到其子类。 Spring中的FactoryBean就是典型的工厂方法模式。如下图： 3. 单例（Singleton） 保证一个类仅有一个实例，并提供一个访问它的全局访问点。 Spring中的单例模式完成了后半句话，即提供了全局的访问点BeanFactory。但没有从构造器级别去控制单例，这是因为Spring管理的是是任意的Java对象。 4. 适配器（Adapter） 将一个类的接口转换成客户希望的另外一个接口。Adapter模式使得原本由于接口不兼容而不能一起工作的那些类...
2018-10-14
534
下一篇

相关文章

发表评论

资源下载

更多资源
Mario

Mario

马里奥是站在游戏界顶峰的超人气多面角色。马里奥靠吃蘑菇成长，特征是大鼻子、头戴帽子、身穿背带裤，还留着胡子。与他的双胞胎兄弟路易基一起，长年担任任天堂的招牌角色。

时间: 2025-12-12 大小: 211.28KB 下载: 54次
Nacos

Nacos

Nacos /nɑ:kəʊs/ 是 Dynamic Naming and Configuration Service 的首字母简称，一个易于构建 AI Agent 应用的动态服务发现、配置管理和AI智能体管理平台。Nacos 致力于帮助您发现、配置和管理微服务及AI智能体应用。Nacos 提供了一组简单易用的特性集，帮助您快速实现动态服务发现、服务配置、服务元数据、流量管理。Nacos 帮助您更敏捷和容易地构建、交付和管理微服务平台。

时间: 2025-12-21 大小: 189MB 下载: 2次
Rocky Linux

Rocky Linux

Rocky Linux（中文名：洛基）是由Gregory Kurtzer于2020年12月发起的企业级Linux发行版，作为CentOS稳定版停止维护后与RHEL（Red Hat Enterprise Linux）完全兼容的开源替代方案，由社区拥有并管理，支持x86_64、aarch64等架构。其通过重新编译RHEL源代码提供长期稳定性，采用模块化包装和SELinux安全架构，默认包含GNOME桌面环境及XFS文件系统，支持十年生命周期更新。

时间: 2026-01-03 大小: 1.42GB 下载: 2次
Sublime Text

Sublime Text

Sublime Text具有漂亮的用户界面和强大的功能，例如代码缩略图，Python的插件，代码段等。还可自定义键绑定，菜单和工具栏。Sublime Text 的主要功能包括：拼写检查，书签，完整的 Python API ， Goto 功能，即时项目切换，多选择，多窗口等等。Sublime Text 是一个跨平台的编辑器，同时支持Windows、Linux、Mac OS X等操作系统。

时间: 2025-12-03 大小: 9.84MB 下载: 39次
手机查看

扫码在手机上查看文章

扫描二维码，手机阅读更方便

热门标签
SpringBoot4 SpringCloud Docker Nacos3 Jdk25 Kubernetes HarmonyOS6 Gemini3 Redis Service Mesh Rocky DeepSeek OpenAi

欢迎您来访！

登录后，您将获得更多功能！
热门文章
联系我们

有任何问题或合作意向欢迎联系我们

Email: 99873273@qq.com

QQ: 99873273

用户登录
用户注册