Explore >> Select a destination
|
You are here 
|
danganiev.me | ||
| | | | |
www.stackchief.com
|
|
| | | | | GraphQL vs REST, including what is REST, what is GraphQL, and the pros and cons of choosing GraphQL vs REST for your web service | |
| | | | |
engineering.zalando.com
|
|
| | | | | Learn how Zalando uses persisted queries, and how we define and think about different levels of stability of our GraphQL schema. | |
| | | | |
janikvonrotz.ch
|
|
| | | | | For my last project I had to build a web application to administrate a MongoDB database. Due to using Meteor quite a lot I heard about Graphql and the Apollostack. Graphql, which is a specification done by Facebook engineers, promises to be the better REST API (which I hope it is). I became curious and decided the build the server API with Apollo. First I tried to evade using the Meteor as build system as I don't want to get too accustomed to this full-stack ecosystem. However, building a live-reload server and client build system in ES6 with Node.js, Babel and Webpack was simply too much work compared to building this simple web app. So in result this was my stack: | |
| | | | |
java-source.net
|
|
| | | |||
