GraphQL acts on the API Gateway

[thangchung]

Currently, we host the GRPC inside out. Everything is seem fine, but this approach looks like has a lot of drawback such as 2 protocols (REST and gRPC) exposed, some of authentication and authorization functionalities are still processing... If we can have a way to work with GraphQL.NET on the server, and apollo-client for the front-end then it can be standardized with the normal use-case in many projects in the world. Just like below but for .NET ecosystem

References:

• https://github.com/serverless/serverless-graphql
• https://github.com/arackaf/booklist/tree/master/react-redux/graphQL
• https://github.com/sysgears/apollo-universal-starter-kit
• https://github.com/nutstick/typescript-react-apollo-starter-kit

[thangchung]

https://github.com/pekkah/tanka-graphql https://github.com/pekkah/tanka-graphql-samples https://github.com/trojanowski/react-apollo-hooks

Jwt with playground: https://developer.okta.com/blog/2018/09/27/build-a-simple-api-service-with-express-and-graphql

Client tools:

• https://insomnia.rest
• https://github.com/imolorhe/altair
• https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj

[thangchung]

https://jeffhandley.com/2018-09-13/graphql-is-not-odata

[thangchung]

Apollo-client vs Redux

ref https://blog.apollographql.com/the-future-of-state-management-dd410864cae2

https://github.com/apollographql/apollo-link-state/tree/master/examples/todo-remote-schema https://www.robinwieruch.de/react-apollo-link-state-tutorial https://hackernoon.com/setting-up-apollo-link-state-for-multiple-stores-4cf54fdb1e00

[thangchung]

• https://github.com/donavon/hook-flow
• https://github.com/benawad/apollo-link-state-tutorial
• https://github.com/Urigo/WhatsApp-Clone-Client-React
• https://github.com/Microsoft/TypeScript-React-Starter