[Question] Should Kratos provide ConnectRPC as an RPC framework?

[mayooot]

I've used Kratos a bit at work and found it pretty elegant and fast. However, I do have a few questions.

For example, Kratos places proto files in separate microservices, and each service has its own third_party directory. In my setup, I prefer placing all proto files in a single repository -- it makes reviewing and managing them much easier, and use buf to generate pb files.

Secondly, I tried using ConnectRPC instead of Kratos's default RPC implementation(which wraps gRPC). It would be great if Kratos cloud provide an option to choose between ConnectRPC and gRPC!

[shenqidebaozi]

Kratos transport is open, and you can freely introduce the implementation you want.

You can implement connectRPC transport and put it in contrib.

[mayooot]

Kratos transport is open, and you can freely introduce the implementation you want.

You can implement connectRPC transport and put it in contrib.

Does Kratos need ConnectRPC? I've wrapped a simple ConnectRPC transport in my project.