[email protected] <[email protected]> On Fri, Apr 13, 2018 at 7:01 AM Arnaud Dematte <[email protected]> wrote:
> Hi Michael, > > > first, thanks for all the good work you've been doing on grpc/node ! > > > I've been working with GRPC for more than a year and I am a bit puzzled > about where NodeJs support is heading. > > > Currently there are 3 ways to handle GRPC client/server from NodeJS: > > - grpc-native-core with dynamic codegen (seems to be using protobufjs > under the hood) > > - grpc-native-core with static codegen (using protoc which unfortunately > requires grpc object to be created using getter/setter which is quite > ill-suited for the ecmascript community) > > - grpc-js-core which is still in alpha and seems to be wrapping protobufjs > to implement the grpc service part which the lib does not handle. > > > We are using Node (typescript) in our node projects and are looking for > the best approach possible. I would personally bet on the native > grpc-js-core because it seems to better fit the javascript ecosystem but what > do you personally feel is the future for grpc in Node ? > > > cheers, > > > -- > Arnaud DEMATTE > > *Chief Innovation Officer * > > *Claranet France – Runiso Critical Data *[email protected] > Office +33 (0) 3 62 13 83 76 <+33%203%2062%2013%2083%2076> > 167 avenue de Bretagne, 59000 Lille > <https://maps.google.com/?q=167+avenue+de+Bretagne,+59000+Lille&entry=gmail&source=g> > www.runiso.com - www.claranet.fr > > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAO8e_2LsJB8kN1e6BCiTd8DuN%2Bkr-QRwQQsAkMZ%2BmKvUKQPfSw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
