GraphQL vs. REST APIs: a complete guide
airplane.dev
GraphQL vs. REST APIs: a complete guide
1–10 of 103 posts
Re: GraphQL vs. REST APIs: a complete guide
#2Just like OOP vs FP. REST is OOP (you start with resource), Graphql deals with function (query and mutation).
Re: GraphQL vs. REST APIs: a complete guide
#3For JavaScript based projects TeleFunc[1] can make development way simpler by 'removing' the need for an API.
Re: GraphQL vs. REST APIs: a complete guide
#4Just like OOP vs FP. REST is OOP (you start with resource), Graphql deals with function (query and mutation).
I'm not following how shifting the resource definition from server-side to client-side makes it any more "FP" than REST.
Re: GraphQL vs. REST APIs: a complete guide
#5imma let u finish, but a hypermedia is a necessary constraint for an API to be RESTful...
edit: more usefully, you need to be really careful w/ your GraphQL end points because they are being access in an untrusted computing environment:
https://intercoolerjs.org/2016/02/17/api-churn-vs-security.h...
my understanding is that facebook whitelists their graphql queries but, last I looked, I didn't see security getting much attention around it...
Re: GraphQL vs. REST APIs: a complete guide
#6Just like OOP vs FP. REST is OOP (you start with resource), Graphql deals with function (query and mutation).
Where does tRPC, where you start with types, fit in?
Re: GraphQL vs. REST APIs: a complete guide
#7Well, seems somebody doesn't care about jsonapi/openapi and the rest of the family.
Sparse field sets / compound documents are nothing new and I'd argue its easy to overlook that there's no magic in the backend for graphql either.
Re: GraphQL vs. REST APIs: a complete guide
#8Re: GraphQL vs. REST APIs: a complete guide
#9Here's how you do it:
- REST/Hypermedia when you're actually building a website (not app) and your "site" is a state machine
- OpenAPI when you expose and API to 3rd parties
- Isomorphic TypeScript APIs when you're using TS on both backend and frontend [0]
- GraphQL when the frontend needs to talk to an API layer provided by different teams
- OpenAPI when one backend talks to another backend
- gRPC might be an option, but most teams don't need it
[0]: https://wundergraph.com/blog/isomorphic_typescript_apis_end_...
Re: GraphQL vs. REST APIs: a complete guide
#10Here's how you do it: - REST/Hypermedia when you're actually building a website (not app) and your "site" is a state machine - OpenAPI when you expose and API to 3rd parties - Isomorphic TypeScript APIs when you're using TS on both backend and frontend [0] - GraphQL when the frontend needs to talk to an API layer provided by different teams - OpenAPI when one backend talks to another backend - gRPC might be an option…
[deleted]