Content
@
0 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
Am I wrong for thinking GraphQL is how builds APIs today? GraphQL as core (anyone can select just the data they need) Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL) and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like What am I missing / where does this go wrong? trying to open my mind on GraphQL https://gist.github.com/tim-smart/e10e4cbaeff35242d8352adead30bef9
7 replies
4 recasts
41 reactions
Alex Loukissas 🍉
@futureartist
I can talk for days for graphql. It's great and it's also not great. Nuances. Best fit for enterprise, for sure.
1 reply
0 recast
3 reactions
artlu 🎩
@artlu
@warpcastadmin.eth pilled me on GraphQL as Lunchbreak scaled to tremendous bursty loads. similar order-of-magnitude boilerplate as Swagger on a framework, plus some backend-frontend type safety like drizzle... Performance seems fine, haven't really had to tune (yet). One-man codebase plus AI assist. You seem to get a decent amount of transparency + flexibility "for free"
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
For free meaning using Apollo? Cc @downshift.eth
1 reply
0 recast
1 reaction
artlu 🎩
@artlu
transparency: lots of tooling for discovery, auto-complete and codegen flexibility: GraphQL parsing vs fixed API endpoints I just happened to use Yoga (lightweight) and graffle née graphql-request (also lightweight) rather than Apollo, but it all works together seamlessly
1 reply
0 recast
3 reactions
