3 ms·
It's fantastic to see a tutorial that separates the frontend from the backend. As someone that _doesn't_ work in web technologies, it can be tough to follow bas
by alexchamberlain 9y ago
It's fantastic to see a tutorial that separates the frontend from the backend. As someone that _doesn't_ work in web technologies, it can be tough to follow basic tutorials or take them to the next level when you're trying to understand node, npm and webpack, as well as the concept you want to learn: GraphQL, which although hyped, does look like it brings substantial value to the table.
- aaron-lebo 9y agoIf you are a starter don't worry about it at this point. A good REST API and understanding of how that works is a really good foundation for web development that you can take with you from language to language and project to project. This is a cool but still relatively niche technology.
- alexchamberlain 9y agoMy interest in GraphQL has a few different layers: it's a different querying paradigm, in the same way that REST and RPC paradigms are different; what are the pros and cons? How do you optimise services throughout your stack to handle load that is - in theory - of an unknown pattern, but in practice, will be of certain shapes? Furthermore, if we divide SOA/microservices into several tiers - separating UI services from backend services - does GraphQL fair better than more traditional paradigms? How do we "merge" GraphQL schemas? Whilst I agree it's niche now, not many new paradigms come along and not many of them have so many questions that can be asked, so there has to be something interesting there.