smallnest
Repos
174
Followers
4208
Following
35

Best microservices framework in Go, like alibaba Dubbo, but with more features, Scale easily. Try it. Test it. If you feel it's better, use it! 𝐉𝐚𝐯𝐚有𝐝𝐮𝐛𝐛𝐨, 𝐆𝐨𝐥𝐚𝐧𝐠有𝐫𝐩𝐜𝐱! build for cloud!

7345
1097

:zap: Go web framework benchmark

1784
192

:zap: Golang Serializer Benchmark Comparison

381
48

rpcx microservice framework in Rust

102
19

unbounded chan

351
50

Events

Created at 1 day ago

Site updated: 2022-11-27 11:00:31

Created at 1 day ago

Site updated: 2022-11-27 10:58:34

Created at 1 day ago

Site updated: 2022-11-27 10:15:37

Created at 1 day ago
Created at 6 days ago

Site updated: 2022-11-21 22:16:37

Created at 1 week ago

Site updated: 2022-11-20 22:33:44

Created at 1 week ago

Site updated: 2022-11-20 22:21:39

Created at 1 week ago
closed issue
远程调用返回参数为map类型时接受不到返回数据

func (h *LogHouse) GetRetention(ctx context.Context, req int64, reply *map[int32][]int64) error {...}

Created at 1 week ago
issue comment
远程调用返回参数为map类型时接受不到返回数据

没有额外信息不确定你具体的方法实现。实现中需要 *relay = newmap

Created at 1 week ago
closed issue
What's the benefit to use QUIC vs TCP, HTTP in RPC area?

Hi maintainer,

I notice rpcx has supported QUIC protocol. Could I know the benefits to use rpcx over QUIC? Is there benchmark to compare the performance with TCP/HTTP/QUIC/KCP?

Trying to see how QUIC does in rpc area? We are evaluating whether we should use RPC over QUIC. Thanks for your information!

Created at 1 week ago
closed issue
目前默认把args和reply参数结构体放入了缓存池,如果没有实现Reset方法,可能会导致bug。

目前默认把args和reply参数结构体放入了缓存池,一出了UserPool参数,如果所有的参数类型没有实现Reset方法,可能会导致不可预期bug。

Created at 1 week ago
issue comment
目前默认把args和reply参数结构体放入了缓存池,如果没有实现Reset方法,可能会导致bug。

fixed

Created at 1 week ago
closed issue
高并发下 Call的args和reply的值会飞

// 服务端调用 func Newe(id int, ver string) (*, error) { def := client.DefaultOption def.Retries = 10 d, _ := client.NewPeer2PeerDiscovery("tcp@"+s.ServerIp, "") s.cliPool = client.NewXClientPool(10000, "strategy", client.Failtry, client.RoundRobin, d, def)

return &s, nil

}

type Sc struct { cliPool *client.XClientPool }

func (s *Sc) Query(sd Data, para ...string) (bool, string, error) { arg := rpcx.Args{Data: sd, Paras: para} rep := rpcx.Rep{}

xclient := s.cliPool.Get()
err := xclient.Call(core.NewContext(), "Queyr", arg, &rep)

if len(arg.Paras) > 0 {
	fmt.Println("调用 Queyr 接口2-----------:", key, arg, rep)
}

return rep.Ok, rep.Data, err

} // 客户端 func (st *Strategy) Query(ctx context.Context, args *rpcx.Args, reply *rpcx.Rep) error { var err error reply.Ok, reply.Data, err = sch.Query(args.Data, args.Paras...) return err } 现在问题是 高并发下 args的值有可能会跟其它协程的参数互相串连,导致args reply的数据都不正常。

Created at 1 week ago
closed issue
有没有可能增加一个接口格式,可以让RPCX方法接口和GRPC保持一致?

grpc接口格式是:

func (this *Greeter) SayHello(ctx context.Context, in *Sample.Request) (out *Sample.Response, err error) {
}

而rpcx接口格式是:

func (this *Greeter) SayHello(ctx context.Context, in *Sample.Request, reply *Sample.Response) err error {
}

有没有可能在rpcx内部通过反射做一个判断,让两种方式都可以支持。当用户实现grpc格式时,rpcx不需要通过pool创建reply对象。 这样可以让通过grpc 实现的方法以最小改动代价迁移到rpcx框架下面。

Created at 1 week ago
issue comment
有没有可能增加一个接口格式,可以让RPCX方法接口和GRPC保持一致?

例子: https://github.com/rpcxio/rpcx-examples/tree/master/handler

Created at 1 week ago
closed issue
按照示例注册服务到consul后,在consul控制面板看不到注册的服务

按照示例注册服务到consul后,在consul控制面板看不到注册的服务

Created at 1 week ago
issue comment
按照示例注册服务到consul后,在consul控制面板看不到注册的服务

不是以consul service注册的,二十以kv格式注册的服务。rpcx服务不是consul的服务

Created at 1 week ago

https://github.com/rust-lang/rust/pull/93563

Created at 1 week ago
started
Created at 1 week ago
issue comment
应用退出后,注册中心etcd 不会自动注销,必须待租约到期

不是

Created at 1 week ago
issue comment
RegisterOnShutdown not work

需要更多的信息或者例子

Created at 1 week ago
issue comment
func (p *EtcdV3RegisterPlugin) Unregister(name string) (err error) log wrong

typo

Created at 1 week ago
closed issue
应用退出后,注册中心etcd 不会自动注销,必须待租约到期

应用退出后,注册中心etcd 不会自动注销,必须待租约到期

这个要怎么处理?

Created at 1 week ago
issue comment
应用退出后,注册中心etcd 不会自动注销,必须待租约到期

应用退出的时候调用server.UnregisterAll

Created at 1 week ago
Created at 2 weeks ago
Created at 2 weeks ago

update kanal version to latest

kanal had too many bug fixes since pre1.

Merge pull request #6 from fereidani/patch-1

update kanal version to latest

Created at 2 weeks ago
update kanal version to latest

kanal had too many bug fixes since pre1.

Created at 2 weeks ago
closed issue
Why v1.1.0 not released yet?
Created at 2 weeks ago