Hacker News Reader

This looks amazing.

So custom resolvers are node cloud functions, right?

It appears that you need a second Node.js server to implement your custom resolvers deployed via docker. This second server merges its schema with the automatically generated schema from PG.

This is a bit disappointing. I was expecting to just "point" parts of the automatic schema to some cloud functions hosted anywhere (Now v2, Lambda, etc) much like what AppSync does. This would bring all the benefits of going serverless and decoupling the schema from implementation. Some cloud functions could be written in Node, but others could be written in Go in a different provider.

You can write your custom resolvers in any language you want, you don't need to use node at all.

> Some cloud functions could be written in Node, but others could be written in Go in a different provider.

Yep, I write mine in Go with Hasura, works great.

So you merge the schemas on every cloud function?

Ah, are you talking about schema stitching? This is coming to Hasura I think.

Edit also see: https://news.ycombinator.com/item?id=18495971

Hey! Hasura founder here :)

Exactly this, we're working on adding remote schema merging into Hasura itself (kind of like AppSync) so this won't be a problem. This should be out very soon!

Awesome!

Reply on news.ycombinator.com