bRPC

<dependency>
    <groupId>com.polyu</groupId>
    <artifactId>netty-client</artifactId>
    <version>1.0-SNAPSHOT</version>
</dependency>

@Component
public class Test {

    @BRpcConsumer(version = "1.0", loadBalanceStrategy = RpcLoadBalanceConsistentHash.class, timeOutLength = 1000L)
    private static HelloService helloService;

    public static void test() throws InterruptedException {
        String yyb = helloService.hello("yyb");
        System.out.println("yyb = " + yyb);
    }
}

bRPC.client.registry.type=zookeeper
bRPC.client.registry.address=127.0.0.1:2181
bRPC.client.registry.target.name=springbootApplication
bRPC.client.timeout.checkInterval=500

<dependency>
    <groupId>com.polyu</groupId>
    <artifactId>netty-server</artifactId>
    <version>1.0-SNAPSHOT</version>
</dependency>

@BRpcProvider(value = HelloService.class, version = "1.0")
public class HelloServiceImpl implements HelloService {
    
    @Override
    public String hello(String name) throws InterruptedException {
        return name;
    }
}

bRPC.server.application.name=springbootApplication
bRPC.server.address=127.0.0.1:12277
bRPC.server.registry.type=zookeeper
bRPC.server.registry.address=127.0.0.1:2181

A netty-based RPC framewor

1. Based on netty NIO, IO multiplexing.
2. The client and server establish a heartbeat packet keep-alive mechanism. When an unknown disconnection occurs, reconnection ensures a reliable long connection.
3. Use kryo serialization, customize the transmission package, and transmission format to avoid TCP packet contamination problems.
4. Support zookeeper or nacos as service registration center.
5. The number of core threads and the maximum number of threads in the server-side business thread pool can be configured in the annotations, and the client can freely choose the load balancing strategy corresponding to the interface through the annotations.
6. Can easily integrate SpringBoot for use.

Getting Start

Start

API startup

1. com.application.test.api.server.ServerTest.java Server start
2. com.application.test.api.client.ClientTest.java Client starts and rpc calls HelloService.hello()

Start integrated with SpringBoot (Because it is not published to a remote warehouse, it needs local maven install.)

1. client

• maven

<dependency>
    <groupId>com.polyu</groupId>
    <artifactId>netty-client</artifactId>
    <version>1.0-SNAPSHOT</version>
</dependency>

• springboot

@Component
public class Test {

    @BRpcConsumer(version = "1.0", loadBalanceStrategy = RpcLoadBalanceConsistentHash.class, timeOutLength = 1000L)
    private static HelloService helloService;

    public static void test() throws InterruptedException {
        String yyb = helloService.hello("yyb");
        System.out.println("yyb = " + yyb);
    }
}

• application.properties

bRPC.client.registry.type=zookeeper
bRPC.client.registry.address=127.0.0.1:2181
bRPC.client.registry.target.name=springbootApplication
bRPC.client.timeout.checkInterval=500

2. server

• maven

<dependency>
    <groupId>com.polyu</groupId>
    <artifactId>netty-server</artifactId>
    <version>1.0-SNAPSHOT</version>
</dependency>

• springboot

@BRpcProvider(value = HelloService.class, version = "1.0")
public class HelloServiceImpl implements HelloService {
    
    @Override
    public String hello(String name) throws InterruptedException {
        return name;
    }
}

• application.properties

bRPC.server.application.name=springbootApplication
bRPC.server.address=127.0.0.1:12277
bRPC.server.registry.type=zookeeper
bRPC.server.registry.address=127.0.0.1:2181

Registry deployment

Docker Zookeeper deployment (example also supports nacos)

1. docker pull zookeeper:3.4.14
2. docker images
3. docker run -d -p 2181:2181 --name b-zookeeper --restart always {imageId}
4. docker ps -a
5. docker exec -it {containerId} /bin/bash
6. ./bin/zkCli.sh