Extension: GraphQL

[dhmlau]

This issue is tracking progress on implementing native GraphQL layer making it easy to build GraphQL APIs in LoopBack.

• Package name: @loopback/graphql
• Example app: @loopback/example-graphql
• Docs: Creating GraphQL APIs

Progress

Stability: ⚠️Experimental⚠️

• feat(graphql): add an extension for type-graphql integration #5545 added the initial implementation of native GraphQL layer, built using type-graphql.
• feat: improve graphql configuration and subscriptions #6313 added support for GraphQL subscriptions
• feat: improve graphql configuration and subscriptions #6313 improved graphql configuration and subscriptions

What's next

We don't have any specific plans now, we are looking for your feedback! Please give the new extension a try and let us know what works for you well and what is missing.

[mpicard]

Looking forward to working on this! 😄

[dhmlau]

added @beeman. Welcome aboard!

[beeman]

Thanks @dhmlau!

[raymondfeng]

FYI: Here are prior arts that integrate GraphQL with LoopBack 3.x:

• https://github.com/yahoohung/loopback-graphql-server
• https://github.com/Tallyb/loopback-graphql
• https://github.com/BlueEastCode/loopback-graphql-relay

[mpicard]

I'd like to look at https://github.com/apollographql/apollo-server as well as incorporating the https://github.com/apollographql/apollo-tracing interface for metrics! Would be cool to enable that.

[dhmlau]

@mpicard , now that you've mentioned apollo, here is another reference too.
https://github.com/gramps-graphql/gramps-express

[mpicard]

@dhmlau very cool project! I wasn't aware of it. Thanks for sharing, the modular aspects of it look great and would be a great for lb!

[stale]

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

[dhmlau]

Still needed!
I wonder if there's any news on this extension. And would it be possible if we can use https://github.com/yahoohung/loopback-graphql-server (just an example) as a reference for implementation?

[ghost]

@dhmlau Any updates with this issue? My team is looking into using LB4 and GraphQL in production, so I'd be interested in providing a helping hand.

[dhmlau]

@peanutenthusiast, thanks for your interest! We’re looking at an approach that would convert your REST APIs into GraphQL APIs. Would that be something fit your need?
It is a bit different from https://github.com/yahoohung/loopback-graphql-server which takes LB artifacts to convert into GraphQL APIs. I can provide more details once we're (or close to) ready.

[ghost]

@dhmlau Yes! This is exactly what my team is trying to do right now. Looking forward to further details.

[jjtang1]

@peanutenthusiast That is awesome to hear, would love you trying it out! Could you share what your team is trying to do just to help us understand the context? Thanks!

[ghost]

@jjtang1 My team is interested in using LB4 as an orchestration layer API to aggregate needed data from different data sources (MongoDB, REST, SQLServer, etc.).

Right now, we're experimenting with a simple GraphQL LB4 server with an mssql connector, will update you and the team as we move further along the process.

[dhmlau]

@peanutenthusiast, we're proud to present to you the oasgraph module that allows you to create GraphQL APIs within the same LB application.
http://v4.loopback.io/oasgraph.html

You can find more info on the integration here (docs will be on its way!): #1775

[bajtos]

I updated issue description to better communicate the current status: we have an experimental version of GraphQL layer and looking for user feedback now.

You can learn more about the graphql extension in our docs: https://loopback.io/doc/en/lb4/GraphQL.html