Architecture / data sources about open-api HOT 5 CLOSED

@ojongerius the idea is to make open-api our primary and sole back-end. So yes this means we will have to recreate the model schema here once again.

I know that's a chore, but in favor of simplicity lets do it. For starters lets make the very first few commits based off of the schema that we have on the main repo.

It is going to be evident that we have to do a hybrid approach for GraphQL and REST, to keep supporting the client side code in the short term.

I propose we just use https://www.apollographql.com

I have seen excellent feedback for them.

We should just ignore, anything Loopback, we aren't going to be using any of its feature. The explorer plugin is not upgraded by us I think, so its not going to work as you have already found.

from open-api.

@ojongerius I just spoke with @raisedadead and @Bouncey and we are in agreement - all data should be exposed through GraphQL.

Our intention is to quickly rip out Loopback and replace it with GraphQL ASAP.

Don't worry about any sort of backward compatibility - we can overhaul all our other tools to work with GraphQL.

from open-api.

@ojongerius Yes - we're planning to use GraphQL for all freeCodeCamp services (except for the forum, which is sort of it's own monolithic app).

I'm closing this issue since we've decided this aspect of our architecture - feel free to open subsequent issues to discuss other considerations.

from open-api.

@raisedadead thoughts? Who would be candidates to chime in? @BerkeleyTrue, @QuincyLarson?

from open-api.

Great! Thanks for the feedback @raisedadead, @QuincyLarson.

There definitely is less overhead in building a server with GraphQL without implementing REST, so I'm all for it. However, the sceptic person in me says that there might be a real possibility that we will have this reality where we'll have to support both while freeCodeCamp gets an overhaul.

Ok, so we are going to convert all models, but can enjoy support from the team in preventing drift between the 2 models while we are cutting over, is that right @QuincyLarson?

from open-api.