Asnyc upload about mouselog HOT 3 OPEN

Hi @winwisely99 , I'm interesting in gRPC. But AFAIK, serving gRPC requires a server-side endpoint too. So what's the best practice to serve both REST (port 80/443) and gRPC (and what port we should use?)? Just add main_grpc.go beside main.go and let it serve gRPC port?

from mouselog.

The answer:

Use GRPC gateway if you want to expose GRPC to Web browsers. Its exposed them as REST.
https://github.com/grpc-ecosystem/grpc-gateway

Use pure GRPC to expose GRPC to non web browsers ( mobiles, desktops, other servers).

Background data:

REST / SWAGGER are not aligned with GRPC.

Gnostic ( https://github.com/googleapis/gnostic) is another way also. You can model your objects using open OpenAPI and then it will compile them to Protobufs.

Too many ways to do things i know. I find GRPC and GRPC Gateway are the best approach as it has a long support history. REST is only useful for basic things i find and has poor perf IMHO.

Let me knwo if this info helps you.

from mouselog.

I think we can put the upload-trace API into gRPC, because it's most frequently used. Can you make a PR about it?

from mouselog.