GoLang與Java各自生成grpc代碼流程介紹
1.背景
由于公司的日志系統(tǒng)使用的是plumelog,最近生產(chǎn)環(huán)境老是報(bào) jedis連接池不夠,導(dǎo)致丟失日志,而且服務(wù)老是重啟,懷疑跟日志系統(tǒng)有關(guān),于是自己改造plumelog,使用go grpc生成server端,使用java grpc生成客戶端,將日志以grpc服務(wù)形式傳遞到server端。
2.go生成grpc代碼
2.1 安裝
protc:https://github.com/protocolbuffers/protobuf/releases
選擇自己所需版本,解壓后將protoc.exe拷貝至go環(huán)境的bin目錄下
2.2 安裝對應(yīng)插件
go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.28
go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.2
將生成的插件拷貝至go環(huán)境的bin目錄下
編寫.proto文件:
syntax = "proto3";
// 指定等會文件生成出來的package
package server;
option go_package = "plumelog/rpc;server";
// 定義request model
message PlumelogRequest{
string message = 1; // 1代表順序
}
// 定義response model
message PlumelogResponse{
string message = 1; // 1代表順序
}
// 定義服務(wù)主體
service PlumelogService{
// 定義方法
rpc GetPlumelog(PlumelogRequest) returns(PlumelogResponse);
}項(xiàng)目結(jié)構(gòu)圖:

在終端cd到proto目錄下,執(zhí)行如下命令生成grpc代碼:
protoc --go_out=plugins=grpc:. server.proto
server端:
main.go:
import (
"google.golang.org/grpc"
"log"
"net"
"plumelog/rpc"
"plumelog/server"
)
func main() {
// 1. new一個(gè)grpc的server
rpcServer := grpc.NewServer()
// 2. 將剛剛我們新建的ProdService注冊進(jìn)去
rpc.RegisterPlumelogServiceServer(rpcServer, new(server.RpcServer))
// 3. 新建一個(gè)listener,以tcp方式監(jiān)聽8899端口
listener, err := net.Listen("tcp", ":8899")
if err != nil {
log.Fatal("服務(wù)監(jiān)聽端口失敗", err)
}
// 4. 運(yùn)行rpcServer,傳入listener
_ = rpcServer.Serve(listener)
}server.go
package server
import (
"context"
"plumelog/rpc"
)
type RpcServer struct {
}
var pushProducer *plumelog.Producer
func (*RpcServer) GetProductStock(ctx context.Context, req *rpc.PlumelogRequest) (*rpc.PlumelogResponse, error) {
fmt.Println(req.Message)
return &rpc.PlumelogResponse{Message: req.Message}, nil
}3.java生成grpc代碼
3.1 idea安裝protobuf插件

3.2 創(chuàng)建maven項(xiàng)目
pom.xml:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>com.plumelog</groupId>
<artifactId>plumelog</artifactId>
<version>3.5</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>plumelog-logback</artifactId>
<name>plumelog-logback</name>
<packaging>jar</packaging>
<dependencies>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
<version>1.2.3</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.2.3</version>
</dependency>
<dependency>
<groupId>com.plumelog</groupId>
<artifactId>plumelog-core</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java</artifactId>
<version>3.5.1</version>
</dependency>
<!-- https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java-util -->
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java-util</artifactId>
<version>3.5.1</version>
</dependency>
<!-- https://mvnrepository.com/artifact/io.grpc/grpc-all -->
<dependency>
<groupId>io.grpc</groupId>
<artifactId>grpc-all</artifactId>
<version>1.12.0</version>
</dependency>
<dependency>
<groupId>javax.annotation</groupId>
<artifactId>javax.annotation-api</artifactId>
<version>1.3.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>javax.annotation</groupId>
<artifactId>javax.annotation-api</artifactId>
<version>1.3.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>javax.annotation</groupId>
<artifactId>javax.annotation-api</artifactId>
<version>1.3.2</version>
<scope>compile</scope>
</dependency>
</dependencies>
<build>
<plugins>
<!-- 依賴包插件 -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/lib</outputDirectory>
<!-- 是否不包含間接依賴 -->
<excludeTransitive>false</excludeTransitive>
<!-- 忽略版本 -->
<stripVersion>false</stripVersion>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.xolstice.maven.plugins</groupId>
<artifactId>protobuf-maven-plugin</artifactId>
<version>0.5.0</version>
<configuration>
<protocArtifact>
com.google.protobuf:protoc:3.1.0:exe:${os.detected.classifier}
</protocArtifact>
<pluginId>grpc-java</pluginId>
<pluginArtifact>
io.grpc:protoc-gen-grpc-java:1.11.0:exe:${os.detected.classifier}
</pluginArtifact>
</configuration>
<!-- <executions>-->
<!-- <execution>-->
<!-- <goals>-->
<!-- <goal>compile</goal>-->
<!-- <goal>compile-custom</goal>-->
<!-- </goals>-->
<!-- </execution>-->
<!-- </executions>-->
</plugin>
</plugins>
<extensions>
<extension>
<groupId>kr.motd.maven</groupId>
<artifactId>os-maven-plugin</artifactId>
<version>1.6.2</version>
</extension>
</extensions>
</build>
</project>maven插件:

3.3 生成grpc代碼
// 這個(gè)就是protobuf的中間文件
// 指定的當(dāng)前proto語法的版本,有2和3
syntax = "proto3";
// 指定等會文件生成出來的package
package server;
option java_package = "com.plumelog.logback.rpc";
option java_multiple_files = false;
option java_outer_classname = "RpcClient";
// 定義request model
message PlumelogRequest{
string message = 1; // 1代表順序
}
// 定義response model
message PlumelogResponse{
string message = 1; // 1代表順序
}
// 定義服務(wù)主體
service PlumelogService{
// 定義方法
rpc GetPlumelog(PlumelogRequest) returns(PlumelogResponse);
}ps:指定的package要與go 那邊的proto指定的package一致,否則啟動報(bào)找不到rpc服務(wù)
雙擊maven插件的protobuf:complie生成rpc代碼,雙擊maven插件的protobuf:custom生成grpc代碼
調(diào)用:
private String rpcHost = "127.0.0.1";
private int rpcPort = 8899;
ManagedChannel channel = ManagedChannelBuilder.forAddress(rpcHost, rpcPort).usePlaintext().build();
@Override
protected void append(ILoggingEvent event) {
if (event != null) {
send(event);
}
}
protected void send(ILoggingEvent event) {
final BaseLogMessage logMessage = LogMessageUtil.getLogMessage(appName, env, event);
if (logMessage instanceof RunLogMessage) {
final String message = LogMessageUtil.getLogMessage(logMessage, event);
PlumelogRpcClient.callRpcServer(channel, message);
}
}package com.plumelog.logback.util;
import com.plumelog.logback.rpc.PlumelogServiceGrpc;
import com.plumelog.logback.rpc.RpcClient;
import io.grpc.ManagedChannel;
public class PlumelogRpcClient {
public static void callRpcServer(ManagedChannel channel, String message) {
RpcClient.PlumelogRequest request = RpcClient.PlumelogRequest.newBuilder().setMessage(message).build();
try {
PlumelogServiceGrpc.newBlockingStub(channel).getProductStock(request);
} catch (Exception e) {
e.printStackTrace();
}
}
}服務(wù)引入log在本地 maven倉庫的坐標(biāo),啟動即可,前提是go 服務(wù)先啟動。
到此這篇關(guān)于GoLang與Java各自生成grpc代碼流程介紹的文章就介紹到這了,更多相關(guān)Go生成grpc內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Go語言編程通過dwarf獲取內(nèi)聯(lián)函數(shù)
這篇文章主要為大家介紹了Go語言編程通過dwarf獲取內(nèi)聯(lián)函數(shù)詳解,有需要的朋友可以借鑒參考下,希望能夠有所幫助,祝大家多多進(jìn)步,早日升職加薪2022-11-11

