@Michael Jones @Emi The basics about the Graphcool backend will not change. You will still get a full back-end with connected database out of the box, just like you are now. There will be some changes in the API, but the basic functionality will remain the same. You will still be able to use that back-end 'as-is' like you are now. The API/Gateway is the emerging answer to a lot of common requirements/questions/features that people using GraphQL are looking for: more control over the exposed schema, more control over authentication, stitching multiple schemas together in one endpoint etc. For this purpose, Graphcool and others in the GraphQL community (like Apollo and myself) have been developing tooling to make this process easier. The boilerplate and tools that Graphcool offer for this purpose are the result of these emerging best practices. So this does not change anything about the back-end offering, it just adds on top of it for those that need the features that it offers.

Thank you, it all had me somewhat lost and nervous. That definitely clears things up however 🙂

@agartha for an ignorant question, it looks like a full node server will be the gateway..? Was it always Node or was it previously in Scala?

Previously, there was no separate Gateway server. The back-end GraphQL server is implemented using Scala/Sangria. The gateway boilerplate uses node, because that's the most common server technology, and most of the tools are available for that platform (like the Apollo

graphql-tools

). However, you are in no way limited to it. You can use any platform you want, including Scala/Sangria if you want. That would however mean more manual work, as these tools are not yet available for that platform.

Awesome, thank you @agartha. That made complete sense.