Differences/considerations between server implementations?

[sui...@gmail.com]

Just starting to look at using gRPC, and quite impressed so far.

I'm wondering if there are any major differences between implementations across different languages when choosing which to use as the gRPC service itself?

E.g. do they all have feature parity, are some considered more tested or production ready than others, etc.?

Mostly looking into choosing between Python/Java/Go.

[Eric Anderson]

Use the language that fits your use-case best. The only language that is "special" is C++, because it is being optimized to a level beyond most other languages, but at a cost of being harder to use to get all that performance. Python, Java, and Go each use a different stack (Python uses the C stack). If you have a very specific need one may be a bit further along than another, but one language isn't always trailing another language out of Python, Java, and Go.

In the OSS world, grpc-go probably has the most services using it. I expect most services using Java are closed-source. And I wouldn't be aware of Python-using services. So grpc-go would probably be easiest to read other people's service code.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/89e2e3d7-25ee-4189-a216-110005405e61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sui...@gmail.com]

Thanks, that's a very good point, there seem to be a lot more examples of Go services to look at.

On Monday, 24 April 2017 17:05:34 UTC+1, Eric Anderson wrote:

Use the language that fits your use-case best. The only language that is "special" is C++, because it is being optimized to a level beyond most other languages, but at a cost of being harder to use to get all that performance. Python, Java, and Go each use a different stack (Python uses the C stack). If you have a very specific need one may be a bit further along than another, but one language isn't always trailing another language out of Python, Java, and Go.

In the OSS world, grpc-go probably has the most services using it. I expect most services using Java are closed-source. And I wouldn't be aware of Python-using services. So grpc-go would probably be easiest to read other people's service code.

On Fri, Apr 21, 2017 at 6:20 AM, <sui...@gmail.com> wrote:

Just starting to look at using gRPC, and quite impressed so far.

I'm wondering if there are any major differences between implementations across different languages when choosing which to use as the gRPC service itself?

E.g. do they all have feature parity, are some considered more tested or production ready than others, etc.?

Mostly looking into choosing between Python/Java/Go.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.